Hi all,
I'm currently in the process of upgrading our systems from using
a Solaris lp (lpsched) system to LPRng.
The current system consists of one print server running 2.5.1
and more than 50 clients - almost exclusively 2.7 (soon will be
completely 2.7). I have basically echoed this setup with LPRng,
with one server, dealing with requests from the clients. On the
machine set up as LPRng print server, I have completely
removed lp and rebooted the machine.
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.
Also, as a side point, can anyone suggest why nlsadmin gives
me this error:
machine% uname -a
SunOS machine 5.7 Generic_106541-12 sun4u sparc
SUNW,Ultra-5_10
machine% nlsadmin -v tcp
nlsadmin: error: Invalid network specification
machine%
Many thanks in advance
Toby Blake
Division of Informatics
University of Edinburgh
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
