-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
chconfig'd my script . . . I did all of this before posting the first time (sorry for not being clearer). The script definitely runs at runlevel 5 (it's status after boot is "running"), but the script isn't started automatically. I guess I'm missing something about init.d scripts. I thought that it would START the script at the particular runlevel.
I don't understand this paragraph. You say that “The script definitely runs at runlevel 5” and later you say that “the script isn't started automatically”. Both affirmations are mutually excluyent, that can not be. Please clarify.
I found this to be odd as well . . . that's why I'm posting. The reason why I say it's running at level 5 is because I set the default start run level to 5 and when I chkconfig'd it it said "rc5.d: on" and then when I check it's status after boot (#/etc/init.d/script status), it says that it's running, but I have no ssh connection. However, I can manually start the script (#/etc/init.d/script start)and, therefore, the ssh connection. So, I say that it's running, yet not started.
You then should say that the init script run, but it is not working >:-) The reason for the failure should be logged in the boot.msg log file. As Verner Kjærsgaard said, I'd check that network and dns is really up at the moment this scripts runs. Anything the script may need should be running already. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknd7o8ACgkQtTMYHG2NR9Xo/ACfWUeMiw4h4k349PeQc86OR/aY YygAn1pZfGrh3njlVUvHPHN/dfkPLHWX =ckRb -----END PGP SIGNATURE-----