ash endless loop after ssh client is killed
Denis Vlasenko
vda.linux at googlemail.com
Sun Apr 29 11:58:48 UTC 2007
On Sunday 29 April 2007 05:53, Alexander Kriegisch wrote:
> Here is the requested strace log. Strace was attached to the 'sh'
> process after the SSH session had been established. The output shows
> what happens when the client is killed:
>
> > $ strace -p 331
> > Process 331 attached - interrupt to quit
> > read(0, "", 1) = 0
> > --- SIGHUP (Hangup) @ 0 (0) ---
> > --- SIGCONT (Continued) @ 0 (0) ---
> > ioctl(0, TIOCSCTTY, {B38400 opost isig icanon echo ...}) = -1 EIO (Input/output error)
> > rt_sigaction(SIGWINCH, {0x10000000, [], 0}, {0x10000000, [], SA_SIGINFO|0x46ebd0}, 16) = 0
> > ioctl(10, 0x80047476, 0x7f8b89dc) = -1 ENOTTY (Inappropriate ioctl for device)
> > setpgid(0, 331) = -1 EPERM (Operation not permitted)
> > rt_sigaction(SIGTTOU, NULL, {SIG_DFL}, 16) = 0
> > close(10) = 0
> > exit(0) = ?
> > Process 331 detached
>
> Should I regard the issue fixed and your suggested change an official
> fix for BB's ash?
Fix is in svn now. Thanks.
--
vda
More information about the busybox
mailing list