Junio C Hamano wrote: > > Somebody I met last week in Japan reported that the socks client > he uses to cross the firewall to connect to git:// port from his > company environment seems to do signal(SIGCHLD, SIG_IGN) before > spawning git. Similar problems occasionally happen with SIGPIPE. There are apps[1] that spawn processes with SIGPIPE set to SIG_IGN giving unexpected results, i.e. child processes that still try to produce output (getting EPIPE on every printf, but who checks printf errors?) even if the pipe-reader (e.g. their parent) is long gone. Ciao, ET. [1] i.e. KDE had this bug - don't know if it's still there. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html