On 04Jun2006 22:21, Jeff Vian <jvian10@xxxxxxxxxxx> wrote: | The default init script does however do a source on /etc/sysconfig/sshd | which does not exist by default. | | Why not put a line in there that can be used by the init command that | actually starts sshd. | $SSHD $OPTIONS && success || failure | $OPTIONS has no value by default, so if something like | OPTIONS="-f /your/config/file" | were put into the specialized sshd file in /etc/sysconfig (or even into | the beginning of the specialized init script) it should work. Can I suggest something far simpler? Keep exactly one config file - it makes getting everything right much simpler and safer - you don't want things getting out of sync. Start the extra ssh daemons from /etc/rc.local with explicit overrides. Example: I do this: /usr/sbin/sshd -p 22 \ -o "ListenAddress $IPADDR" \ -o "PidFile /var/run/sshd-$NET_IF.pid" on my laptop to start per-interface sshds with specific pid files. The variables $IPADDR and $NET_IF come from the script I drive this with, but I'm sure you get the idea. In this way you can say "start and sshd exactly as normal except for these changes", and everything is very clear. Cheers, -- Cameron Simpson <cs@xxxxxxxxxx> DoD#743 http://www.cskk.ezoshosting.com/cs/ Agree, for Law is costly. -- Very good advice to litigious Persons, founded upon Reason and Experience; for many Times the Charges of a Suit exceed the Value of the Thing in Dispute. - Bailey's dictionary, 1736 -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
