I have created a script that is supposed to run a certain service at boot time. Let’s call it “script”. I saved “script” to /etc/init.d. I made sure it can use “start” and “stop” as a parameter when ran manually(ex. /etc/init.d/script start). I went ahead and created symbolic links in rc3.d and rd5.d to point to this script. When executing the command ls -l you will see something like:
SXXscript → …/script and KXXscript → …/script
with no red highlighting to indicate error on my part. When I reboot the server the script does not run at all. I created an echo statement and a redirect to a file at a certain path at the beginning of the script for debug purposes (echo “running script” > /path/debugfile) and this file is not created, so I know the script is never looked at. Is there a certain configuration that disables new scripts to be added to rcX.d directories? Any help is appreciated.
> I have created a script that is supposed to run a certain service at
> boot time …] and created
> symbolic links in rc3.d and rd5.d to point to this script. …]
> When I reboot
> the server the script does not run at all.
The SuSE init script mechanism by default does not use these symbolic
links anymore. But you can get back the old behaviour by editing the
config file /etc/sysconfig/boot and setting RUN_PARALLEL=“no” therein.
If you want your skript to work properly with SuSE’s enhanced init
system, start from /etc/init.d/skeleton to get the proper header and
then activate your script via the insserv command which creates not
only the symbolic links for the old RUN_PARALLEL=“no” operation but
also the entries in SuSE’s hidden dependency files which control
operation under RUN_PARALLEL=“yes”.