Bug 3409 - smbd always tries to connect to CUPS despite printing=lprng
smbd always tries to connect to CUPS despite printing=lprng
Status: RESOLVED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: Printing
3.0.20b
x86 Linux
: P3 normal
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-14 13:50 UTC by Paolo
Modified: 2006-01-18 13:15 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paolo 2006-01-14 13:50:54 UTC
Distro is Slackware 10.2
smbd is flooding syslog with lines like those below. 
I have LPRNG in place and printing=lprng in (G). Tried to 
set it under [printers], then removed [printers] at all,
load printers = no - no change.
Tried to set debuglevel to 0, but seems to fail:

root@gnu:~# smbcontrol smbd debug 0
root@gnu:~# smbcontrol smbd debuglevel
PID 19510: all:1 tdb:1 printdrivers:1 lanman:1 smb:1 rpc_parse:1 rpc_srv:1 rpc_cli:1 passdb:1 sam:1 auth:1 winbind:1 vfs:1 idmap:1 quota:1 acls:1 locking:1 msdfs:1

how can I convince smbd I have no CUPS and make it stop asking?

-- paolo

Jan 14 21:19:56 gnu smbd[19508]: [2006/01/14 21:19:56, 0] printing/print_cups.c:cups_cache_reload(122) 
Jan 14 21:19:56 gnu smbd[19508]:   Unable to get printer list - server-error-service-unavailable 
Jan 14 21:19:56 gnu smbd[19508]: [2006/01/14 21:19:56, 0] printing/print_cups.c:cups_cache_reload(85) 
Jan 14 21:19:56 gnu smbd[19508]:   Unable to connect to CUPS server localhost - Connection refused 
Jan 14 21:35:05 gnu smbd[19508]: [2006/01/14 21:35:05, 0] printing/print_cups.c:cups_cache_reload(122) 
Jan 14 21:35:05 gnu smbd[19508]:   Unable to get printer list - server-error-service-unavailable 
Jan 14 21:35:05 gnu smbd[19508]: [2006/01/14 21:35:05, 0] printing/print_cups.c:cups_cache_reload(85) 
Jan 14 21:35:05 gnu smbd[19508]:   Unable to connect to CUPS server localhost - Connection refused
Comment 1 Gerald (Jerry) Carter 2006-01-17 21:30:41 UTC
Make sure you set 'printcap name = /etc/printcap'.  Otherwise
I expect your default is stillset as 'printcap name = cups'.
We can't really do this automatically since the printcap name 
is a global option and printing is a service level option.
Comment 2 Paolo 2006-01-18 00:56:55 UTC
thanks, that seems to fix the problem indeed.

I was misleaded by the man smb.conf which say:

printcap name 
            ...
            Default:
                   printcap name = /etc/printcap

but seems undefined here. So in such case smbd defaults to trying all 
systems in turn, despite printing = lprng? 
I'd rather avoid smbd checking cups if not explicitly told so.
Comment 3 Gerald (Jerry) Carter 2006-01-18 08:28:57 UTC
The actual default value for the 'printcap name' is 
determined by the compile time detection of the default
'printing' value.  The best way to see that is by running 
`testparm -v -s /dev/null | grep print`
Comment 4 Paolo 2006-01-18 13:15:59 UTC
(In reply to comment #3)
> The actual default value for the 'printcap name' is 
> determined by the compile time detection of the default
> 'printing' value.  The best way to see that is by running 
> `testparm -v -s /dev/null | grep print`
> 

yep the manual say so as well... lazy me. The point is that such msgs
appeared in syslog after some upgrade, so the packager seems to have
changed his mind (and perhaps I went through the changelog too quickly).

Thanks! :)