Hi, On Wed, Feb 15, 2006, Ryan Lovett wrote: > Why couldn't it contact a remote CUPS server running DBUS?
Hmm, I just discovered that DBus can be used over TCP/IP, sorry for the misinformation. > > If you're on a network with lots of machines and a central server, you > > should consider installing cupsys on invidual machines (which should be > > the default already). > Its much easier to set ServerName in client.conf to the central server > rather than distribute all the configuration files to each of the clients > and keep them up-to-date. Its also more appropriate in my opinion; the load > caused by the polling really does seem like buggy behavior. A Solaris print > system doesn't demonstrate this behavior, for example. (though it is of > course much more feature barren than CUPS.) I do agree that the rate is high (it was probably chosen so that the icon appears promptly after a documents is printed), I don't want to debate that, however running a local cupsys has other advantages, such as queuing of documents in case the main server is down. I feel it's quite logical to have a local spool of print jobs, just like I feel it's sensible to have a local MTA or a retry mechanism in your MUA. My position is that running a cupsys on each machine is a sensible thing to do for practical advantages, and also works around the central server hammering problem you're having. Cheers, -- Loïc Minier <[EMAIL PROTECTED]> Current Earth status: NOT DESTROYED
