ignoring SIGPIPE causing problems in pipes

[Ed L Cashin]

Markus Friedl <markus.friedl at informatik.uni-erlangen.de> writes:

> On Sat, May 26, 2001 at 05:52:33PM -0400, Ed L Cashin wrote:
...
> > Ideally, a SIGPIPE in a filter caused by the process on stdout exiting
> > would result in ssh exiting, maybe with a "Broken pipe" diagnostic.
> > In the context of forwarding, though, SIGPIPE would be ignored when
> > appropriate.
> > 
> > It's just a guess, but it seems like a signal handler for SIGPIPE
> > could be written that decides what do do based on whether forwarding
> > is in effect or not.
> 
> btw, did you try
> 	ssh -n ?

Hmm.  It works in the trivial cases I tried, but not in the case I'm
most interested in; namely, restoring from a dump streamed via ssh
from a remote host.

-- 
--Ed Cashin                   PGP public key:
  ecashin at terry.uga.edu       http://www.terry.uga.edu/~ecashin/pgp/