Hi Toby,
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...
hope this helps, best regards
~christoph
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
On Wed, 13 Nov 2002, Toby Blake wrote:
> I'd like to say thanks for all the replies to this, it seems to me
> that this is probably not the sort of thing that I would like to do on
> a long term basis, but would be fine in the short term. I'll explain
> why I want to do this.
>
> We have a system whereby I would like to easily swap one print server
> in to take the place of another one, for maintenance, upgrade or
> whatever. This could be done in one of two ways - either change the
> printcap information held in LDAP, or change the print server alias to
> point to another machine, e.g. host1 has an alias of print1, host2 has
> an alias of print2 - if I want to take host2 down, I can change the
> print2 alias to point to host1.
>
> The trouble is, our system uses ldap and dns servers on every local
> machine which sync with the masters every hour (different machines
> will sync at different times to reduce the load). This means that any
> changes made to ldap or dns will take between 1 and 60 minutes to
> propagate to any one host.
>
> So, in the example above, in the one-hour period after changing the
> alias, I need both host1 and host2 to be able to spool to the same
> printers, as various clients will resolve print2 differently.
>
> Phew.
>
> 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.
> -----------------------------------------------------------------------------
>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
