Colin Watson reports that gnome-session has been known to leave
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Wed, 2 Mar 2011 19:12:42 +0000 (19:12 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Wed, 2 Mar 2011 19:12:42 +0000 (19:12 +0000)
commit203abf9e5d58b7ca053ae30c231c7e7eac8edfb9
treee2b757c071266bfd019591d4e4303c0712ac3bd8
parent4f1aa9a9cacee7dffea752607b5ad6c254f3e28b
Colin Watson reports that gnome-session has been known to leave
SIGPIPE ignored in its child processes, leading to unexpected
behaviour inside pterms. (The gnome-session I'm sitting in front of
doesn't seem to do this as far as I can tell, but I don't doubt there
are some that do.) Add SIGPIPE to the list of signals we reset to
default behaviour before launching pterm's child process.

git-svn-id: svn://svn.tartarus.org/sgt/putty@9117 cda61777-01e9-0310-a592-d414129be87e
unix/uxpty.c