Date: Wed, 2 Jan 2002 15:13:59 -0500 From: Charlie & <root@pr0n.kutulu.org> To: Joe Halpin <joe.halpin@attbi.com> Cc: "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG> Subject: Re: System trying to start sshd twice Message-ID: <20020102151359.D946@pr0n.kutulu.org> In-Reply-To: <3C31EE53.991457@attbi.com>; from joe.halpin@attbi.com on Tue, Jan 01, 2002 at 11:13:55AM -0600 References: <3C31E06B.6300D48F@attbi.com> <3C31E736.1000908@potentialtech.com> <3C31E908.655652E4@attbi.com> <3C31EC4D.1020902@potentialtech.com> <3C31EE53.991457@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 01, 2002 at 11:13:55AM -0600, Joe Halpin wrote: > supplied executables. Guess I should have also modified /etc/rc.conf at > the same time. You basically have two options here. Since the port installed it's own startup script, you could have simply set sshd_enable="NO" in rc.conf, and the system would skip it's own sshd boot code. Or, you could set the sshd_program and sshd_flags variables in rc.conf, and the system would start the ports version at boot time. Personally, I prefer this method for programs that are in the base system, as I think it's easier to undo the change if/when the base sshd (or whatever) moves up to the latest version. --K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020102151359.D946>