On Thu, Dec 18, 2014 at 3:08 PM, Chet Ramey <chet.ra...@case.edu> wrote: > > What the original complaint refers to is what to do in the infrequent > case when the terminal goes away, the kernel doesn't deliver a SIGHUP, > and a read returns EOF instead of -1. >
I cannot reproduce it in anyway. I flooded the session leader and foreground process (far below in the child-parent tree) with signals, some of them trapped, some ignored, and closed the xterm on touch /tmp/somefile typed in. nothing. either something abnormal must happen in the system in order to reproduce this, or this bug is not visible on my environment. maybe it is something in local setup. Jiri: I think you should describe in details the remote and local systems, for example what terminal are you using, how are you connecting to the remote host? also please tell us if it is reproducible. cheers, pg
