Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NIS Shutdown`

Status
Not open for further replies.

inforeqd

Technical User
Jan 8, 2001
95
US
Ok. I believe this is in the way it shutdown (i.e. the order). So

RHEL 3.0 Server. Nis is installed, working and its all good. The only problem I have is that when I do a reboot I get the following:
do_ypcall" clnt_call RPC unalbe to receive errno= Connection refused

I believe this is due to the shutdown of ypserv before ypbind goes down. So, how can I get it to shutdown ypbind first?

The rationale behind this theory is that if I manually kill ypbind and then do a reboot its all good.

TIA
inforeqd
 
check the first lines of /etc/init.d/ypserv and /etc/ini.d/ypbind

with a man chkconfig.
You could find something like this:
RUNLEVEL FILES
Each service which should be manageable by chkconfig needs two or more commented lines added to its init.d script. The first line tells chkconfig what runlevels the service should be started in by default, as well as the start and stop priority levels. If the service should not,by default, be started in any runlevels, a â should be used in place of
the runlevels list. The second line contains a description for the service, and may be extended across multiple lines with backslash continuation.

For example, random.init has these three lines:
# chkconfig: 2345 20 80
# description: Saves and restores system entropy pool for \
# higher quality random number generation.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top