Hi, My initial question: The Solaris 2.6 system gave me the following error message: "inetd: couldn't find ISTATE environment variable. Try -s flag." during reboot. After reboot, inetd did not start. This error should come from the last line of /etc/init.d/inetsvc - '/usr/sbin/inetd -t'. When I do 'inetd -t' manually, I got this error message again, and inetd couldn't be started. When I do 'inetd -s' manually, inetd is started. Answer: In /etc/init.d/inetsvc, the last line should be '/usr/sbin/inetd -s'. I have no idea when and HOW it became '/usr/sbin/inetd -t' in my system. Changing '-t' back to '-s' solved the boot problem. Some people indicated that the problem is probably because 'sac' is not running according to the manpage. Actually sac is running well after reboot (Is it possible that sac is not running and you can still use the system? Try to kill 'sac' to see what interesting thing will occur, if you have a test system as well as the interest.) The basic question remains: Why 'inetd -t' does not work when sac is running? Can anyone answer it? Thanks: Casper Dik, Alex Bell, Storta, John S, laloo yadav, Bob Metcalf, Kevin Buterbaugh (lost one email sorry) Melissa Young System Administrator _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Dec 20 08:59:17 2001
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:31 EST