This page exists simply to provide a few keywords to hopefully help people find the odd clue for a technical hitch that didn't turn up a lot of hits in the search engines when I was struggling with it.
A few such issues are collected here: CLUESTICK


2006-08-22

Samba "Unable to connect to CUPS Server" errors


By default, if your samba is compiled with CUPS support, but you haven't yet configured CUPS & printers.. you get your logs filled with junk like this:

[2006/04/30 05:14:05, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/04/30 05:14:05, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/04/30 05:14:05, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/04/30 05:30:05, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused

What a pain in the arse. What were those kooky (but revered!) samba developers thinking?
Just because CUPS support is compiled in.. doesn't mean the samba server should default to madly probing for a local CUPS server and spewing into the logs.

Most of my samba servers will never be print servers... but any one of them may at some stage need to become one. i.e I don't know at install time if it'll be needed - but it's nice to be able to install from the same samba package with CUPS support - and know it's available easily without a samba reinstall if needed.
Sheesh.. how about a sensible set of defaults.. like.. I dunno.. printer sharing is just plain OFF by default??
(Surely I'm not alone in this.. and the majority of samba servers don't actually have printers??)

According to this, you can stop the thing whinging by adding the following lines to your smb.conf
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes


ju li-an at vector-stream dot com
(remove the dashes to email)

Valid XHTML 1.0!