hi,
on my clients I use something like:
<printer_name_on_client>:\
:rm=<server1>,<server2>:\
:rp=<queue_on_server>:\
:sd=<spooldirectory>:\
:mx#0:
naturally the binaries must be LPRng, though the server binaries don't
need to.
I just tried it on the 3.8.1 version (I'm running an older one) and it
runs there too without any problems, you probably have a syntax error (?)
regards
~christoph
On Tue, 4 Dec 2001, Osman, Mohamed wrote:
> Yes, that's exactly what I was trying to do,
> except it is not working for me.
>
> I tried the following:
>
> rm=server1,server2
>
> but all I get back when I do lpstat is: no server active,
> and it attempts to open connection with server1,server2
> as one word, which is not what I wanted. I have tried
> separating space after the comma but that did not help
> either.
>
> Any idea what I am doing wrong? An example printcap would
> help.
>
>
>
>
>
>
> Regards,
>
> Mohamed
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 03, 2001 12:26 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: LPRng: How to setup print server redundancy/redundancy
>
>
> hi,
>
> there is a cool undocumented feature in LPRng which might be ineresting
> for you: if you create an entry like rm=<spool1>,<spool2>,<spool3> on your
> client all the mentioned server will be tried. I use this on ~2000 UNIX
> clients with 2 servers and it works perfect.
>
> regards
> ~christoph
>
>
>
>
>
>
> On Fri, 30 Nov 2001, Osman, Mohamed wrote:
>
> > Hi,
> >
> > I have few centralized UNIX Print Servers with lprng and
> > several hundreds UNIX clients that use them. The print
> > servers in turn send the jobs via LPD to Windows Print
> > Servers. The reason that was done this way is that we
> > do not maintain the Windows servers.
> >
> > So a typical printcap on the clients looks like this:
> >
> > *:\
> > :sd=/var/spool/lpd/printers:\
> > :mx#0:\
> > :sh:\
> > :rm=server-name
> >
> > This works as you expect, but we wanted to route
> > the jobs (fail over to other servers) if the above
> > server were to crash w/o impacting the users.
> >
> > I have updated the printcap file to look like this:
> >
> > *:\
> > :sd=/var/spool/lpd/printers:\
> > :mx#0:\
> > :sh:\
> > :rm=server1
> > #
> > *:\
> > :sd=/var/spool/lpd/printers:\
> > :mx#0:\
> > :sh:\
> > :rm=server2
> >
> > The intention was if a particular printer is not available on
> > server1 then server2 will be searched, or if server1 was down
> > then all jobs will be routed to server2. That's not was is
> > happening. At all time only server2 is searched, in other words
> > the last entry is the one looked at.
> >
> > Has anyone attempted doing similar thing? Is there anything in
> > the documentation that deals with this issue that I have overlook
> > at?
> >
> >
> >
> >
> > Thanks,
> >
> >
> > =====================================
> > Mohamed Osman
> > NW Engineering Computing
> > Intel Corp
> > Email: [EMAIL PROTECTED]
> > =====================================
> >
> >
> >
> ----------------------------------------------------------------------------
> -
> > 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.
> ----------------------------------------------------------------------------
> -
>
> -----------------------------------------------------------------------------
> 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.
-----------------------------------------------------------------------------
