wow,

great feature, is it mentioned in the HOWTO ? 

It should be interesting for most people working on large scale
environments, especially when you have a couple of linux pcs instead of
one big server doing the spooling...

thanks for the great support on this list Patrick !!!

Christoph




[EMAIL PROTECTED] schrieb:
> 
> > From [EMAIL PROTECTED] Wed Aug  2 10:39:22 2000
> > Date: Wed, 2 Aug 2000 12:27:01 -0400 (EDT)
> > From: Lars Kellogg-Stedman <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: Failover
> >
> > I'm setting up a new printing architecture at <random company X>, and we'd
> > like to make sure people can continue printing when our primary print
> > server fails.
> >
> > We will shortly be setting up a duplicate print server (one that is
> > synchronized against the master nightly using rsync), but I haven't been
> > able to figure out how to do any sort of failover with the LPRng clients.
> >
> > All of our client systems are running lpr in "client-only" mode -- no local
> > lpd; all jobs go straight to the server.  I'd like the clients to do
> > something like this:
> >
> >   IF the primary print server is available THEN
> >       print to the primary print server
> >   ELSE IF the secondary print server is available THEN
> >       print to the secondary print server
> >   ELSE
> >       die gracefully
> >
> > Is it possible to do anything like this?
> >
> > -- Lars
> >
> > --
> > Lars Kellogg-Stedman <[EMAIL PROTECTED]> --> http://www.larsshack.org/
> 
> You can use:
> 
> lp:lp=pr@host1,host2
> 
> OR
> 
> lp:rm=host1,host2
> 
> This does what you want, I believe.
> 
> h4: {92} % lpq -Pt1@h1,localhost
> Printer: t1@h4  'Test Printer : 1'
>  Queue: no printable jobs in queue
>  Status: job 'papowell@h4+746' removed at 17:11:05.416
> 
> This has been in LPRng for a long time.
> 
> Patrick
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------

-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------

Reply via email to