On 04.Dec.2000 -- 02:03 PM, Toby Blake wrote:
> This all tests OK and I have been printing using lprng for quite a 
> while from server *and* clients, but looking at the HOWTO 
> document I see that it really strongly recommends a reboot as 
> part of the switching from Solaris lp to lprng.  I'm wondering if 
> other people have made this same change and if they have 
> found it necessary to reboot - it would be a huge disruption to us 
> to have to reboot all of our machines - many people run long 
> running jobs, some of these machines are servers, etc.

No problem without the reboot. Guess it's for the sake of those having
problems with the complicated procedure to remove lpd from inetd.conf,
kill -HUP inetd, kill lpd to be shure.

Although this is only a small setup, I'm quite happy with LPRng over
here and quite like the aproach to distribute printcaps through nis :-)

        Christian Haul

-- 
Technische Universit�t Darmstadt        +49.6151.16 -6232 (Tel) / -6229 (Fax)
Datenbanken &  Verteilte Systeme        
http://www.informatik.tu-darmstadt.de/DVS1/staff/haul/
C h r i s t i a n        H a u l        PGP-Key: 
http://www.informatik.tu-darmstadt.de/DVS1/staff/haul/pgp.html
[EMAIL PROTECTED]         FPR: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 
335A 9E08

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