ignoring SIGPIPE causing problems in pipes

[Markus Friedl]

On Sat, May 26, 2001 at 05:52:33PM -0400, Ed L Cashin wrote:
> Markus Friedl <markus.friedl at informatik.uni-erlangen.de> writes:
> 
> > i'm not sure what the right thing to do is in this situation.
> > clientloop.c needs to ignore SIGPIPE, because of all the
> > portforwarding code needs this. should select() return if 'sed'
> > dies?
> 
> I'm not familiar enough with the code to know how the forwarding
> issues relate to the SIGPIPE in a filter situation.  
> 
> 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 ?