I recently upgraded from Samba 3.0.2a to Samba 3.0.11. I didn't change anything in my smb.conf file. But Now, when a user logs on to my Linux server and access a Samba share, in the log file for that machine there is always a message repeated twice: [2005/03/16 05:40:23, 0] printing/print_cups.c:cups_cache_reload(85) Unable to connect to CUPS server localhost - Connection refused As far as I can tell, I do NOT have any CUPS lines in my smb.conf file. I have CUPS running as a service on my machine (which I should probably stop), but I don't want to make any printers available to network users. Any clues as to why this error message is appearing now, and it never appeared with Samba 3.0.2a? Andy Liebman
On Wed, 16 Mar 2005 08:57:32 EST, AndyLiebman@aol.com <AndyLiebman@aol.com> wrote:> I recently upgraded from Samba 3.0.2a to Samba 3.0.11. I didn't change > anything in my smb.conf file. > > But Now, when a user logs on to my Linux server and access a Samba share, in > the log file for that machine there is always a message repeated twice: > > [2005/03/16 05:40:23, 0] printing/print_cups.c:cups_cache_reload(85) > Unable to connect to CUPS server localhost - Connection refused > > As far as I can tell, I do NOT have any CUPS lines in my smb.conf file. I > have CUPS running as a service on my machine (which I should probably stop), > but I don't want to make any printers available to network users. > > Any clues as to why this error message is appearing now, and it never > appeared with Samba 3.0.2a?Probably because configuration detected cups was installed on the machine and thus compiled Samba to use it. You should rerun Configure again with --disable-cups to stop that from occurring. David
Hi,
Here is what the chapter on Printing (Chapter 19. Classical Printing
Support) from Samba How-To says:
Only when the parameter is explicitly set to would Samba conform with my
intentions. So, my strong advice is:
* Never rely on commented out parameters.
* Always set parameters explicitly as you intend them to
behave.
* Use testparm to uncover hidden settings that might not
reflect your intentions.
So you not having CUPS in your smb.conf does not mean system does not
have it by default.
Prakash
<AndyLiebman@aol.com> wrote:> I recently upgraded from Samba 3.0.2a to Samba 3.0.11. I didn't
change> anything in my smb.conf file.
>
> But Now, when a user logs on to my Linux server and access a Samba
share, in> the log file for that machine there is always a message repeated
twice:>
> [2005/03/16 05:40:23, 0] printing/print_cups.c:cups_cache_reload(85)
> Unable to connect to CUPS server localhost - Connection refused
>
> As far as I can tell, I do NOT have any CUPS lines in my smb.conf
file. I> have CUPS running as a service on my machine (which I should probably
stop),> but I don't want to make any printers available to network users.
>
> Any clues as to why this error message is appearing now, and it never
> appeared with Samba 3.0.2a?