> I think I have good news for you :-) > > There is a somehow not documented failover feature in LPRNG which > works just perfect for your case I think (I use it with >2500 UNIX > clients and have no problems). You can put a list of servers in the > client printcap: 'rm=<spooler1>, <spooler2>, <spooler3>' if > <spooler1> is not available, <spooler2> will be tried and so > on... Of course it will not work if <spooler1> is somehow internally > 'broken' but still accepts jobs, but as soon as it does not accept a > job the failover will take place...
Thanks for this info Christoph - to work this way I would need to re-implement certain parts of our printing system, but it certainly looks like something I should consider when I get the chance. Also, thanks to everyone else who replied to my mails on this, in the short term I will just let two servers handle the same queues, for the couple of hours that maintenance requires. Note that all our print servers run the same version of LPRng. Cheers 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. -----------------------------------------------------------------------------
