[EMAIL PROTECTED] a e'crit: > second spooler. Also if you got 100 jobs in one queue on one server the > job on the second server will most likely wait for a long time because > the printer port will not get unlocked during printing the 1000 jobs from > the first server. Generally it probably depends on your local environment
My personal experience seems to contradict that, and would, in a different way, discourage the use of more than one server. We have a primary printer server which serves all the normal print jobs. Once in a while, I would send a print job off to the secondary server, to be printed on the same physical printer. If there are 10 jobs already waiting on the primary server, the job that I just queued on the other server should rightfully wait for its turn after those 10 jobs. But that ain't the case. The printer seems to take requests from the two servers alternatively. As a result, my "other" print job gets served as soon as the current print job on the primary server is completed. This is a great feature for those who wish to jump the queue (like I do from time to time for my personal stuff), but is probably not ideal for most normal purposes. Regards. ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
