[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SIGPIPE not properly reset with 'trap - PIPE'
|
From: |
Andreas Schwab |
|
Subject: |
Re: SIGPIPE not properly reset with 'trap - PIPE' |
|
Date: |
Thu, 11 Dec 2008 19:51:36 +0100 |
|
User-agent: |
Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux) |
Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> 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?
When SIGPIPE is ignored then the syscall returns with EPIPE instead.
This is what bash is reporting.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."