[EMAIL PROTECTED] wrote:
>
> > 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.
>
In our environment we don't use any kind of printcap-file as well
as no local lpd-daemon, on the LPRng client side.
The lp, lpr & friends (bundled with LPRng), only knows the location
of the lpd.conf file (defined at compile time),
which is located on a NFS-mounted filesystem.
The lpd.conf file consists of one single line:
default_remote_host=server
Is this a supported configuration in LPRng?
It does work very well, but should it?
While reading this thread I thougt that:
default_remote_host=server1,server2,...
would work...
...but is doesn't. The binaries only reads the first value
of the field, which is "server1". The second value "server2"
will never be quered.
At the moment LPRng-3.6.12 is used but I'm configuring a new
server which will run LPRng-current (LPRng-2.6.22).
Is the above described configuration known to work in a more
current LPRng releases?
BR /Johan
--
Ericsson Network Core Products
Unix Systems Management [EMAIL PROTECTED]
Box 1505 Phone: +46 8 727 30 95
S-125 25 �LVSJ�, Sweden Fax: +46 8 647 82 76
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
