On 22 Dec 1998, Niels [ISO-8859-1] Möller wrote:
> From your earlier bug report, it seems that it is the child process
> which dies of EPIPE, when attempting to write to its stdout. Is that
> correct? I think the first target to look closer at is the use of
> shutdown(). Either lsh, your shutdown(), or the code to workaround the
> shutdown() bug in linux-2.0.33, may be broken.
/bin/id works if I make SHUTDOWN defined as 0 (but doesn't close the
connection after running it. Indeed it doesn't close the connection also after
bash. It's already in the TODO ;).
If I make SHUTDOWN defined as shutdown, then it does the same thing as
previously.
Bash works quite strange... I don't get prompt string, but the porgrams work.
(But control chars (eg. ctrl-P) doesn't.)
According to stty: standard input: Invalid argument
Ooops. Maybe we aren't a real terminal? Only a simple stdin-stdout (dumb
terminal)? Obviously this is true, because we don't do anything for being a
registered terminal with a login shell on the remote machine.
I checked it with my old 1.2.21 ssh on my box: the same behaviour occures,
when I say "ssh localhost bash", but if I say "ssh -t localhost bash" then I
get the correct shell. The ssh sais:
' -t Tty; allocate a tty even if command is given.'
So we may need to allocate a terminal (pseudo-tty).
I still can't get how this really works, but this may
get into the TODO...
Keresztg
+ Keresztfalvi Gabor
+ Student of Technical University of Budapest
+ mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
+ http://www.piar.hu/~keresztg/ Pubkey: finger [EMAIL PROTECTED]
