Yep. It says to use /etc/rc.config and put "-4" in the sshd options. Didn't work. In the meantime, I have seen that this doesn't happen consistently. Given the other problem I am having with ADSL right now, I am not going to bother with it now. Cheers, Sean On Sunday 24 February 2002 01:47, Stuart Powell wrote:
Hello, Theo.
If you read the SDB article more closely, Solution 1. tells you how to stop the error message by editing rc.config (easiest via YaST) in order to stop sshd loading up the second time for IPv6.
Bye for now, Stuart.
-----Original Message----- From: Theo.Sean Schulze [mailto:tschulze@nuthole.de] Sent: 19 February 2002 05:44 To: suse-linux-e@suse.com Subject: Re: [SLE] sshd can't bind to port 22
Thanks, that does help out. Now I know sshd is trying to start twice and that SuSE says that they know it is happening. Funny though that the fix is to just ignore it.
On Monday 18 February 2002 18:40, Chris Kuhi wrote:
On Monday 18 February 2002 17:51, Theo.Sean Schulze wrote:
While trying to fix my monitor's invalid scan problem, I rebooted the machine. When it came back up, sshd failed to start. A glance in /var/log/messages shows:
Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
You didn't say which distro/version you're using, but if it's SuSE 7.3, this might be what you're looking for: http://sdb.suse.de/en/sdb/html/tsaupe_kde_startmsg.html
hth, chris
-- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker