|
From: Jamie C. <jca...@we...> - 2006-06-06 16:35:47
|
On 6/Jun/2006 03:27 and...@fr... wrote .. > If I add a new action, a new file is added to my /etc/init.d directory. > > If I put that job on startup at boot time, a link to that file is created > in the (on example) /etc/init.d/rc3.d > > If I reboot the box, the job doesn't start. I suspect that the use of the runlevel 3 link is the problem here.. > I noticed 4 things about that job > > 1) the link is absolute, not relative; almost all are link to ../jobname; > the new one is linked to /etc/init.d/jobname That won't cause any problems .. as long as the link points to the right file, it will work. > 2) the name is S99jobname, instead of a lower number (last used is, on > example S15jobname, so in principle S16jobname should be created (I > think....) Generally, all user-created actions should have high priorities like 99. The low priorities like 15 are usually for criticial system-related scripts which must run first. > 3) on older systems I saw two links ; SxxJob Name and KyyJobName; here > I > see only S99JobName The K script is run when the system shuts down. However, for most servers it is not necessary. > 4) If I add a new job, and also put that in startup automatic, another > S99NewJobName link is created (again absolute link) > > I am using Webmin 1.270-1.noarch.rpm, just upgraded to the last fix; > My operating system is Suse Linux 10.0, kernel 2.6.13-15.10-default I think that the underlying problem may be the way Webmin creates the init.d script. What does the chkconfig: line at the top of the script contain on your system? - Jamie |