On 20/10/11 9:26 PM, Perlover wrote:
Good day, Matt! Hey Perlover
Thanks for nice job Thank you for saying so, it's the least I could do for such a nice community. But i think the best way to describe exactly runlevels in init.d script If there will be '-' then "chkconfig service on" will create only start scripts for default runlevels '2345' but it will not create stop scripts for levels '016' (to checkup by seeing to ls -l /etc/rc.d/rc6.d/K* after chkconfig ... on) So if your some_website file will be included to a system start-up scripts through "chkconfig service on" command the Dancer application will be stopped at shutdown (6 runlevel) only by killall script by kill signal (i think better way by your 'stop' command - service some_website stop at stop priority as your '15')
Perlover I have implemented your addition to the script and explicitly placed the runlevels of 2345 in the init script but am afraid I do not see the difference. This is most likely due to my ignorance of the SysV init system.
If I have #chkconfig: - 85 15 and perform chkconfig some_website on I get symlinks rc3.d/S85some_website, rc5.d/S85some_website, rc4.d/S85some_website and rc2.d/S85some_website If I have #chkconfig: 2345 85 15 and perform the same command I get exactly the same symlinks. I suppose my confusion comes from thinking there should be K15some_website symlinks in rc6.d and rc0.d for the halt and reboot runlevels. I found I can only get K15some_website if I perform a chkconfig some_website off Could you shed some more light on this subject please ? Cheers Matt