Problems with 7.5.2 client not starting up at reboot time
Mike,
I'm guessing that you have set nsrports.... starting with 7.5, the code to start up is flawed.
You have to make sure that nsrports -S does *NOT* include 7937 and 7938. Those two ports are
hard coded and will be used no matter what nsrports says to do -- but including them in the
range causes other processes to use them and then you get error messages in the
/nsr/logs/daemon.raw file that say the port was already in use... with no idea which port!
Easiest way is to instead of using something like
nsrports -S 7937-7940
instead do
nsrports -S 7939-7949
(notice I didn't change the ending port... because 7937 and 7938 will really be used, I just
can't tell networker that it is allowed to use them or it will use them at the wrong time)
Frank
On 3/9/10 9:33 AM, Michael Borkowski wrote:
We've upgraded a number of Linux and Solaris clients to 7.5.2 (Build
452) and noticed that many clients don't start after the machine has
been rebooted. Our server is running Solaris 7.4.5 (Build 746). Anyone
see this problem?
Thanks.
---
mike
Mike Borkowski
University of Waterloo
type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--
Frank Swasey |
http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
