On tisdagen den 2 februari 2010, Magnus Holmgren wrote: > On måndagen den 1 februari 2010, Adam C Powell IV wrote: > > lsh-server fails to configure on mipsel, as can be seen in the buildd > > log for scalapack: > > > > Setting up lsh-server (2.0.4-dfsg-6+b1) ... > > Creating lsh random seed file (this may take a while) ... done. > > Creating lsh host key ... ................ > > .. > > > > done. > > Starting secure shell v2 server: lshdClosed spurious fd 3 > > failed! > > Can someone please check if there's any syslog output from lshd? I've successfully tried installing lsh-server on a virtual mipsel machine under QEMU. I could really use some help here. I think there's also a bug in lam, though. Either liblam4 should merely suggest lam-runtime, or lam-runtime should merely suggest ssh-server, or it should prefer a specific ssh-server implementation. On onsdagen den 3 februari 2010, Niels =?UTF-8?Q?M=C3=B6ller wrote: > Magnus Holmgren <firstname.lastname@example.org> writes: > >> Starting secure shell v2 server: lshdClosed spurious fd 3 > > I also think this message is suspicious. lshd tries to close all fd:s > between 3 and getdtablesize() (to avoid that any spurious open fd leaks > to user processes it spawns). Expected result is that all these close > calls should fail with EBADF. So what is fd 3, and why is it open? Probably the pipe for writing commands to Debconf. I could try closing it, but I don't think it's the problem as lshd started successfully in spite of it when I tested. -- Magnus Holmgren email@example.com Debian Developer
Description: This is a digitally signed message part.