Niels Möller wrote:
Pontus Skoeld pont_lsh@soua.net writes:
No, it won't, (at least for you to be able to use tcpserver, lshd would have to accept to handle one session from stdin/stdout and then exit, which it doesn't).
Actually, it shouldn't be too hard to fix this. Look at src/daemon.c:daemon_init. That function should return DAEMON_INETD if lshd has a connected socket on stdin/stdout (is inetd startup compatible to tcpserver?). Currently, lshd just exits with an error message in this case, but it should be fairly straight-forward to wrap the socket fd in an lsh_fd object and start the initial handshake.
Maybe a feature for 1.5.4? ;-) I'm not able to apply the changes you mention myself, but if you provide a patch and want me to test it, that's no problem.
Regarding your question re tcpserver (from http://cr.yp.to/ucspi-tcp/tcpserver.html): "tcpserver waits for connections from TCP clients. For each connection, it runs prog, with descriptor 0 reading from the network and descriptor 1 writing to the network. It also sets up several environment variables." I don't know if this helps.
Btw, I experience the same connectivity lag as another person mentioned some time ago on the list (only read about it in the web archive of the list, don't have the actual mail at hand). I'm connecting to a host in the U.S. over DSL from Germany (using Putty under Win32), and OpenSSH is much more responsive (no matter if I enable TCP_NO_DELAY in Putty or not).
Regards Jochen