Scot L. Harris wrote on Mon, 24 Oct 2005 09:40:29 -0400:
> Most of the times I have seen this it is caused due to having IPv6
> enabled. ssh binds to the port on IPv4 address or IPv6 then tries to
> bind a second time to the same port.
This makes sense, thanks! I wonder, why it doesn't happen on Suse, though. ipv6
is also running there, but no such error message.
>
> Personally I usually disable IPv6 and the zero conf stuff on systems.
Add "alias net-pf-10 off" to modprobe.conf and reboot? Do I need to do anything
else?
What do you mean with "zero conf stuff"? That is obviously something I'm not
aware of.
> But don't count on that action. Backups are good to have of any
> configuration files you have changed.
Actually, I edit all my config files on my workstation and then transfer the
file to the server machine it belongs to. I maintain a mirrored directory
structure of all our machines with the most relevant config files and all
changed files locally and also carry them around on my laptop. It's so much
easier for comparing configuration and in case you need a fast backup, yes :-)
Kai
--
Kai Sch?tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org
