|Create the link: /etc/init.d/boot.d/S20boot.sysctl
|
|cd /etc/init.d/boot.d
|
|total 8
|drwxr-xr-x 2 root root 4096 Oct 19 19:20 .
|drwxr-xr-x 11 root root 4096 Dec 17 21:39 ..
|lrwxrwxrwx 1 root root 12 Oct 19 19:20 S01boot.proc
|-> ../boot.proc
|...
|lrwxrwxrwx 1 root root 16 Oct 19 19:20
|S10boot.ipconfig -> ../boot.ipconfig
|lrwxrwxrwx 1 root root 12 Oct 19 19:20 S10boot.klog
|-> ../boot.klog
|
|ln -s /etc/init.d/boot.sysctl S20boot.sysctl
|
|lrwxrwxrwx 1 root root 12 Oct 19 19:20 S10boot.klog
|-> ../boot.klog
|lrwxrwxrwx 1 root root 23 Dec 17 22:03 S20boot.sysctl
|-> /etc/init.d/boot.sysctl
Good for you, but don't do it this way on SUSE. The symlink will get
wiped out from the boot.d directory the next time you run SuSEconfig
which is basically anytime after a new package has been installed or YOU
has updated packages. The reason is SUSE recomputes the dependencies
between init scripts when reconfigured and assign the sequence number
using this information, which is why you'll see they are squashed
towards zero instead of being all over the place between 0 and 99.
Instead, look at /etc/init.d/skel and make your init script have those
metadata lines. Then use chkconfig or /sbin/insserv to install that
script.
--
Received on Wed Dec 17 2003 - 23:09:16 CST
