> I'm using "su" (GNU sh-utils) version 2.0 on a RedHat Linux 6.2 box. I also > have OpenSSH 2.9.9p2 running on this box. I wanted to do remote monitoring > of this system's messages, so I logged in using a normal user account then > did a "su --command='tail -100f /var/log/messages' root". > > However, late in the evening when the system is inactive and the sshd daemon > disconnects the session due to lack of activity the "su" process is left > hanging and has to be terminated manually. Is that expected behavior? I > would think that if the parent process dies then the "su" process would > gracefully terminate.
Thanks for the report. I believe you have experienced the ssh "hang on exit" problem. This is a problem often discussed on the [EMAIL PROTECTED] mailing list. If you search the archives there you will find endless debate and discussion about ssh and a "hang on exit" bug. If I am mistaken and it is not that particular issue then I am guessing that it would be that ssh did not propagate the hangup signal to its children. Which was a well known problem and in their TODO list to be fixed. But I thought that one had gotten fixed already by 2.9.x but perhaps not. You can start here: http://www.mindrot.org/pipermail/openssh-unix-dev/2001-December/date.html Bob _______________________________________________ Bug-sh-utils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-sh-utils