Re: [webmin-l] problem with bootup and shutdown action

[Kris D. <kd...@vi...>]

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

Ummm...  I don't know of any SysV-style init system that uses a 
directory like that.  You probably mean /etc/rc.d/rc3.d or /etc/rc3.d. 
(Unless this is a SuSE-ism.)

However, Webmin should be bright enough to recognize the variant and put 
the appropriate symlinks in place.

> If I reboot the box, the job doesn't start.
> 
> 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

Shouldn't be an issue.

> 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....)

The numbers indicate the order daemons start up in, not the order they 
were created in.  Figuring out what order to start various services in 
is a bit of an art;  most "local" services are started last unless they 
MUST start before something else.

> 3) on older systems  I saw two links ; SxxJob Name and KyyJobName; here I
> see only S99JobName

The details on this will vary;  strictly speaking there should be ONE 
symlink to the init script in each rc?.d directory - typically Snn 
(startup) in rc3.d, rc4.d, and rc5.d (and rc2.d on Debian);  Knn (kill 
or shutdown) in rc0.d and rc6.d.  *Most* services will have a Knn link 
in rc1.d as well, but a few critical things will have Snn.

Google "sysv init" for more details on how the whole thing fits together.

> 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

When you reboot, do you see any expected output from your new job?  Most 
init scripts present output of some kind indicating roughly what they're 
doing, any errors, and a final "OK/FAIL" indicator.

What tools does SuSE provide for manipulating system startup and 
shutdown tasks or jobs?  What do they say about the init script and 
symlink Webmin installed?  IIRC SuSE has a few automated tools that 
meddle with things they really shouldn't (like, oh, say, third-party 
changes to the init system).  Check from a shell and see if your custom 
startup jobs are still there.

-kgd