On Mon, 17 Jan 2000, Drew Berendts wrote:

I have developed a couple start-up scripts that I am running out of /etc/rc.d/, including a customized version of sshd. When I attempt to start sshd via /etc/rc.d/rc2.d/S20sshd (as a symbolic link to /etc/rc.d/sshd, the default for using SuSE's sshd install via yast), the script will not run @ startup. I can manually run the script, however, w/out any problems from the /etc/rc.d and /etc/rc.d/rc2.d levels. File permissions are the standard 744, w/ root & group ownership rights of root:root. Anyone have any ideas what may be causing this?

SuSE's scripts typically don't run at startup unless the correct variable is set in /etc/rc.config. Example from latest SuSE sshd rpm: ----- # Force execution if not called by a runlevel directory. test $link = $base && START_SSHD=yes test "$START_SSHD" = yes || exit 0 ----- If you copied code from Red Hat, etc., they typically have similar checks in them against their config files so that if you run them "by hand" outside of the /sbin/init.d/rc context, they will run regardless of config file settings. Also, the "real" rc script directory in SuSE is in /sbin/init.d; /etc/rc.d is just a symlink to /sbin/init.d. Your symlinks in rc?.d should be relative to the parent directory; e.g.: cd /sbin/init.d/rc2.d ln -s ../sshd S20sshd Make sure that you can run your symlinks from /sbin/init.d/rc?.d. Hope that helped. If not, I suggest posting your script. -- Ron Oliver (mailto:roliver-suse@quantum-networks.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/Doku/FAQ/