Re: SIGPIPE not properly reset with 'trap - PIPE'

[Ralf Wildenhues]

Hello Andreas,

* Andreas Schwab wrote on Thu, Dec 11, 2008 at 10:13:18AM CET:
> Ralf Wildenhues <address@hidden> writes:
> 
> > foo: line 20: echo: write error: Broken pipe
> > foo: line 21: echo: write error: Broken pipe

> > Please also note that the above errors occur also when
> >   trap '' PIPE
> >
> > is used instead of 'trap - PIPE'.
> 
> You probably have SIGPIPE ignored when you start the script.  From
> POSIX:
> 
>     Signals that were ignored on entry to a non-interactive shell cannot
>     be trapped or reset, although no error need be reported when
>     attempting to do so.

That may well be, but if SIGPIPE is ignored upon script startup, then
the shell should not output those error messages upon receiving the
signal in the first place, no?

Cheers,
Ralf