[Savannah-hackers] Re: lsh-1.4 still having the same problem

[Niels Möller]

Loic Dachary <address@hidden> writes:

>       I don't but the problem repeats itself for the non-pty case every
> day. 

Now I have tried to reproduce the problem. I did it as follows:

* I started the lshd server,

* logged in using lsh localhost,

* in a different window, looked for my bash login shell, started by
  lshd, 

* killed the lsh process (using RET ~ ., which makes it call exit()
  with no hand-shaking with the server).

* After this, my login process had disappeared.

I then repeated the same thing but with lsh -nt localhost (disabling
the pty allocation), and I killed that client process with kill -9.
Again, my login shell disappeared as expected.

In your earlier mail on this problem, there were both a bunch of bash
processes, with pty:s, hanging in read, like

140     0 10234     1   0   0 19044 17648 poll  S    ?          8:05 
/usr/local/sbin/lshd --enable-core --daemonic --ssh1-fallback=/usr/sbin/sshd 
--trace --verbose
100  1000 21923 10234   0   0     0    0 read_c S    pts/6      0:00  \_ -bash

and you had cvs server processes like

100 61923 15428     1   0   0  2036  924 wait4  S    ?          0:00 sh 
/usr/local/bin/cvssh -c cvs server
000 61923 15429 15428   0   0  2748  948 select S    ?          0:00  \_ cvs 
server
040 61923 15434 15429   0   0  2752 1060 wait4  S    ?          0:00      \_ 
cvs server
000 61923 15435 15434   0   0  3156 1900 select S    ?          0:00          
\_ /usr/bin/editor /tmp/cvsv1pAzV

(I don't quite understand this, though, why is /usr/bin/editor running
on the server, on a non-interactive (i.e. no pty) login???)

As the lsof output also indicated that the lshd process didn't have
any pipes open to non-interactive children.

I'd like to know if this is still what the hanging processes looks
like. And if so, I'd like to know what the /usr/local/bin/cvssh and
/usr/bin/editor programs are doing.

Regards,
/Niels