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