General comments about /etc/cups/client.conf: ---------------------------------------------------------------
By default, CUPS.org ships its source code with a client.conf file that is not active, and we also do not recommend that you use it by default for standard workstations that are part of a LAN. *If* you use a a client.conf file, you're telling your system print commands to use "spoolerless" or "daemonless" printing. It means no *local* spooler or daemon is contacted, instead "lp" or "lpr" contact the named remote print spooler/daemon directly. Usually, printing without local spooling is not is recommended. For example, it will block your client's user interface if there is a network problem and the remote spooler can not be contacted. "daemonless" or "spoolerless" printing is meant for systems with very little resources (embedded systems, diskless systems, etc.). Unless you know what you do, make sure you have *no* "ServerName 11.22.33.44" or "ServerName cups.server.com" entry in a client.conf file. (Caveat: I'm not overly familiar with Gnome+CUPS printing. Since Gnome's CUPS printing support was not exactly stellar for a long time, I did not use it a lot. It may well be that Gnome CUPS Manager does only work if there is a client.conf file around. If this is so, that would be a rather poor implementation, even a design blunder). Oh, and just to give a complete picture concerning client.conf: ------------------------------------------------------------------------------------- * CUPS 1.1 looks for files $HOME/.cupsrc or /etc/cups/client.conf (in that order) to find the "Servername some.cups.server" setting. * Obviously, /etc/cups/client.conf is under root's control and determines the system defaults for all local users. And the .cupsrc file of course enables the user to override the system defaults. * CUPS 1.2 looks for $HOME/.cups/client.conf and /etc/cups/client.conf). If it finds these settings, it uses them. * All above settings may be overriden by the existence of a CUPS_SERVER environment variable. * All above settings are overriden by giving the "-h some.cups.server" commandline parameter. If CUPS does not find any settings in these files or in the env var, it simply assumes and uses "-h localhost". If none of these does work, it will tell you "lp: unable to print file: server-error-service-unavailable". -- /etc/cups/client.conf missing in Dapper Drake https://launchpad.net/bugs/49855 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
