> It is a bad idea for the same reason a printer spooler was invented > in the first place: a printer cannot print two things at the same > time and iterleaving two printjobs isn't particular useful. This was > for a unix systems with many logged in users, each of which needs to > print something. Things doesn't change very much with network > printers and printing from multiple workstations; the printer can > still only print one thing at a time, and for that reason having > only one spooler being in charge of the printer will ensure > everything runs smoothly. All other systems will then submit their > print jobs to that spooler instead of directly to the printer. > > For a set of spooler systems to access one single printer there must > be a protocol to coordinate that access. In the LPD protocol there > is no such mechanism.
I should probably comment that I plan to operate like this for a very short period of time, basically it's a way of getting one print server to serve another print server's queues while it's being upgraded, but because of the nature of our ldap propagation mechanism (ldap is the source of the princap information) there's no way of being entirely sure which of our clients will be looking at the correct server at any one time - update propagation to clients takes up to an hour, unless manually enforced. I have run some simple experiments with two lprng print servers serving the same printer and they seem to operate OK - if the printer is busy, lprng on either machine waits until it's free, effectively queueing jobs in both print servers. Toby ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
