-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
| | I'd hasten to point out that the log snippit indicates to me that | it's being *unsuccessfully* restarted. It's starting, failing to | bind to port 22 as something else is already there, and then dying | off. If this was due to a system update, I'd assume that the old | daemon would be killed off before a new one would be started. | | It just failed to bind to port 22 on 0.0.0.0 - that does not mean that it did not successfully restart. Mine gives the same log entry on every restart but works OK. I'd be glad to know what is the exact meaning of this "failure", but just out of the pure curiosity, since the "failure" does not prevent sshd from operating normally: "if it ain't broke don't fix it".
Regards, Maxim.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCIQEVrv8VoNvub1QRAs5uAJ0Yvt2My2iS4FDpThQHnT9fqHiJ1ACgnGHj 8hyvAj7mvY7dop1IaLhywdc= =gOol -----END PGP SIGNATURE-----
