Re: System trying to start sshd twice
There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. I had this when I forgot that 4.4 installs sshd as a default and reinstalled it from /usr/ports. I just removed the /usr/local/etc/ entry, since I'm going to rerun buildworld, etc., after 4.5-RELEASE. (I'm running 4.5-PRE #2 right now) MLS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
From: Mike Squires [EMAIL PROTECTED] Date: Wed, 2 Jan 2002 09:09:36 -0500 (EST) Sender: [EMAIL PROTECTED] There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. I had this when I forgot that 4.4 installs sshd as a default and reinstalled it from /usr/ports. I just removed the /usr/local/etc/ entry, since I'm going to rerun buildworld, etc., after 4.5-RELEASE. (I'm running 4.5-PRE #2 right now) OK. Let me try to explain what is happening and the appropriate response based on what version of sshd you want to run. You have installed the ssh port which means you probably have 3.0.1 or 3.0.2. You are running 4.5-Prerelease, so you have 2.9 installed in the base system. If you have sshd_enable=YES in /etc/rc.conf, rc will start 2.9 from /usr/sbin. To prevent this from happening, edit your /etc/rc.conf file and comment out the sshd line. If you have /usr/local/etc/rc.d/sshd.sh, v3.0.? is being started. If V2.9 is already running, this will fail. To prevent the system from trying to start V3, pkg_delete openssh or chmod 644 /usr/local/etc/rc.d/sshd.sh. Unless you have a specific reason to run V3 of openssh, I'd really suggest that you stick to the installed, standard V2.9. It's not quite the latest and greatest, but it does get all security patches and is consistent across FreeBSD systems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
On Tue, Jan 01, 2002 at 10:14:35AM -0600, Joe Halpin wrote: There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. This should only be the case if you installed a local copy of sshd (from ports or something). The base system doesn't have *any* startup scripts in /usr/local/etc/rc.d. Assuming you only want one copy of sshd running, you should be able to safely remove the sshd.sh script from /usr/local and set all of the startup parameters in /etc/rc.conf. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
On Tue, Jan 01, 2002 at 10:51:20AM -0600, Joe Halpin wrote: Bill Moran wrote: Joe Halpin wrote: There is code to start sshd in both /etc/rc and /usr/local/etc/rc.d/sshd.sh. Did you install an upgrade to sshd from a port or something? I don't recall doing that, but I must have. The version in /usr/src/crypto/openssh is 2.9, but pkg_info says that the installed version is 3.0.1. Installing something from ports that also exists in the base system doesn't uninstall the parts of the base system. It installs a new copy of the program in the /usr/local tree, leaving the default copy in the /usr tree. You can manually remove the ssh programs from /usr if you want to save space. Also, adding the line: NO_OPENSSH= true to /etc/make.conf will prevent future builds of your source from building the OpenSSH code and reinstalling it. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: System trying to start sshd twice
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 [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
