nis start order issue
 

I have NIS servive (i.e ypbind service) which is configured to run at start level 27 & i have tomcat server startup script which is configured to run at start level 99, this script start the tomcat with an user account "adm" which
is defined in NIS server.For this script to work ideally the YPBIND services should start first.

I am having an issue in which i am getting the following error in /var/adm/messages,in which it shows the init script "startTOmcat" cannot be started as the required NIS user doesnt exist. My NIS service is getting invoked after the "startTomcat" script. Is there any way by which i can change this start order of NIS service as currently it is configured to run at order 27.please help
When i checked the /var/log/messages , i found the following errors :-
++++++++++++++++++++++++=
Nov 20 15:30:34 adm startTomcat: /bin/su user adm doesnt exist
+++++++++++++++++++++++++

Just a few points that occur to me

1. normally we use the word 'level' to refer to init levels (0-6) and start number for individual scripts in a given init level dir eg rc3.d

2. given that 27 < 99, that should work; it sounds like you've got a problem in your NIS setup or maybe firewall.
http://www.linuxhomenetworking.com/w...onfiguring_NIS

3. generally /var/adm/messages => Solaris, /var/log/messages => Linux.
Can you clarify exactly which Unix/Linux we are talking about (inc version/release num)

I mean start order of YPBIND service is 27 & that of "startTomcat" script is 99.When my machine boots the tomcat script didnt starts & when i check the Linux (Red hat) /var/log/messages file i found that
NIS Bind is getting started afterwards my "startTomcat" script inspite its start order is 27.
When the machine boot up completes i am able to execute the "startTomcat" script manually.

Please suggest what can be the issue.


Thanks for your help

What system are you using?

It might also help to have a listing of the rc3.d directory (single column).