On 2012/07/10 16:03 (GMT-0500) Dale Schroeder composed:
Felix Miata wrote:
...
[2012/07/10 14:57:42.225332, 0] printing/print_cups.c:110(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2012/07/10 14:57:42.228331, 0]
printing/print_cups.c:487(cups_async_callback)
failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
...
[2012/07/10 15:38:14.843530, 0] printing/print_cups.c:110(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2012/07/10 15:38:14.846530, 0]
printing/print_cups.c:487(cups_async_callback)
failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
Can whatever is causing smbd to attempt these two processes be made
not to, and stop the recurring resource waste? My only printer is an
IP printer, so AFAICT, Samba is never involved with printing from any
machine on my local network, and I expect it never to be.
http://lists.samba.org/archive/samba/2006-February/117184.html
As I had stripped out or commented every line that looked print or cups
related from smb.conf, this is quite an unexpected response. I thought with
no printing configured in smb.conf, which I thought for the server only, that
those messages must be created by some unknown/tough to discover client
operation.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
