FYI FWIW: What we do at our "large" site is (basically) put
a print server in each building that is the "printhost" for
the printers in that building. Note that the printcap file
is the SAME everywhere ... so EVERY host knows about ALL printers;
but (ideally), each printer should only have ONE print server
that connects to it. A presentation on how we use LPRng can be seen at:
http://www.komar.org/ -> Misc. Tech Stuff -> LPRng
While there was nothing preventing us from having a SINGLE
print server site-wide, the idea was that by doing by building/area;
we keep network traffic somewhat local, and also when there are
power/network outages, we don't clobber people in other buildings.
alek
P.S. The "DNS CNAME" concept mentioned in other Emails is an
excellent idea ... unfortunately, the "MX idea" of multiple records
and different priorities doesn't apply ... so not an easy way to
do this type of failover using DNS.
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
