You can actually place the script anywhere, just create a symbolic link
withan uppercase 'S' or 'K' and the appropriate number. You can call the
link whatever you like.
ex:
You have a script called apache in /root.
cd /etc/init.d/rc3.d
ln -s /root/apache S80start_web_server
cd /etc/init.d/rc1.d
ln -s /root/apache K50stop_web_server
/root/apache must be executable and owned by root.
However, ideally, scripts are placed in /etc/init.d and symbolically linked
from the appropriate run level directory. It is also good practice to name
the symbolic link the same as the script, ie: S80apache. You also need to
look when other services are stopped/started and decide on a logical place
in the sequence to start/stop your process. There is no need to start a web
server before you interfaces and routing have been configured..
On a sidenote, to disable something from starting/stopping automatically,
rename the link to a lower case 's' or 'k' so you can always reference where
it used to be.
Hope this helps,
CC
----- Original Message -----
From: "Mark Hounschell"
Back in 6.4 to add a startup scipt for init all you had to do was place it in /sbin/init.d and then make Sxxscript Kxxscript links in the run-level dir tree off init.d. I know the locatation has changed to /etc/init.d but it seems that the process must have changed also as I can't get it to work doing the same thing as I did in 6.4. Whats the new trick?? Yes I've read some of the docs. The only thing different that I see is something about insserv. Is that the key to getting this to work. It doesn't seem to help me.
-- Mark Hounschell dmarkh@cfl.rr.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com