On Tue, Aug 04, 2009 at 02:04:31PM -0500, Mike Coleman wrote: > This scenario is not something that will happen accidentally, since > there's really no way to SIGSTOP the child without doing it from > another shell, so the prospect of a user ending up in front of a > "hung" shell doesn't seem like that much of a problem.
Perhaps your question rather might be: should SIGSTOP be handled like SIGTSTP?
