severity 567945 normal thanks On lördagen den 24 juli 2010, Magnus Holmgren wrote: > On torsdagen den 17 juni 2010, you stated the following: > > Hi, > > > > sh4 has the same problem.
What is sh4 by the way? > > There was the following logs in syslog. > > ---- > > Jun 17 05:38:44 localhost lshd[26143]: lshd: Could not bind any address. > > ---- > > The problem probably is that while lsh-server.postinst creates > /etc/ssh/sshd_not_to_be_run, it doesn't actually stop sshd. > [...] > Still though, I find it strange that lsh-server would be installed if > openssh- server is already, since that would fulfil lam-runtime's > ssh-server dependency. Of course, if you install lsh-server in a chroot, pbuilder or otherwise, and an SSH server is installed outside it, binding port 22 will still fail, and there's not much that can be done about that. You would probably get exactly the same result if openssh-server were to be installed instead of lsh-server, because the former's postinst also fails if sshd can't be started. In summary, if you install lsh-server when there is already an sshd listening on port 22 you *have* to choose a different port for lsh-server, and having any package build-depend (indirectly) on ssh-server is probably a bad idea. -- Magnus Holmgren holmg...@debian.org Debian Developer
signature.asc
Description: This is a digitally signed message part.
