On Fri, 26 Jan 2001 [EMAIL PROTECTED] wrote:

> centralized:
>     advantages:
>             a general and unique queue for each printer (easy to know  when a job
> is going to be printed, priority ...)
>             we can use the Allow Tables to restrict the access to the printer and
> take advantage of the lpd.perms features to manage the print server node
>     disadvantages:
>             it just depends on one node

I tinkered for a while with various failover software to do hot failover
to a second print server.  Unfortunately, the print daemon under SCO is
total crap (hence the central LPRng server), and would hang if there was
any loss of connectivity with the target print server.

I was using heartbeat, and was using rsynch regular to copy spools to the
backup server (just in case, so I could recover at least some current
print).

Right now, I just keep the second server static and my spools/filters up
to date.  If the prime dies, I just change the IP on the second one, bring
it up, then go about the job of restarting lpd/lpsched on all the SCO
boxes (argh!).

The current LPRng box is a K6/233Mhz/64MB/10GB (5GB spool partition on
reiserfs), kernel 2.2.1x.  It handles print to around 100 printers
(delegating about a dozen printers to LPRng servers in other cities), and
runs through about 7000-10000 jobs a day.  The total, though, is only a
couple hundred megs a day because this is all text--reports, invoices,
pick-slips, and the like.

PS:  As someone else mentioned, a lot of Jetdirect-style cards have
difficulty accepting jobs from multiple servers at once, which is another
reason we used a centralized server.

-----------------------------------------
Brad Hartin - [EMAIL PROTECTED]
Communications Administrator
Straus-Frank Enterprises Limited



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

Reply via email to