Re[2]: Upgraded sshd, now a notice on boot?

[ Available lists | Index of freebsd-questions | Month of Mar 2002 | Week of 8 Mar 2002 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Michel Weenink <Michel@Weenink.com>
Date
8 Mar 2002 05:25:30
Subject
Re[2]: Upgraded sshd, now a notice on boot?
Message-ID
217755450.20020308142804@Weenink.com

In reply to
References to

[ Hide this part ]
 

Friday, March 08, 2002, 1:46:12 PM, you wrote:

S> On Fri, 8 Mar 2002 11:31:24 -0000
S> "James Green" <james@stealthnet.co.uk> wrote:

>> I upgraded openssh from ports yesterday following the security notice.
>> Everything went fine, and on reboot I got a cannot bind to 0.0.0.0
>> notice. Ssh still works, though.
>> Any idea what this might be and is it a problem?

S> Off the top of my head... you're likely running two instances of sshd
S> now.

Could very well be as on most boxes I used to have /usr/sbin/sshd
while the new port/package/source went into /usr/local/sbin/sshd

I don't think I set a prefix on the earlier install. But it's a bit
tricky to keep them both.

HTH,

Michel

--
Michel Weenink - Phone: +31 24 3607 665 - ICQ: 21018820
E-mail : Michel@Weenink.com - WWW: www.weenink.com

I drink therefore I am twice


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Elapsed time: 0.279 seconds