[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tee logs no output if stdout is closed

From: Eric Blake
Subject: Re: tee logs no output if stdout is closed
Date: Mon, 29 Sep 2008 05:55:58 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080914 Thunderbird/ Mnenhy/

Hash: SHA1

According to Bruno Haible on 9/26/2008 8:10 AM:
>> I know this condition arises only when ignoring or handling SIGPIPE,
>> (which should be rather unusual) but even so, I really dislike the idea
>> of ignoring a write error.  Even if the write error would not occur
>> with slightly less output data, it's still one less _legitimate_ error
>> that can be reported.  If there is an EPIPE error, IMHO, close_stream
>> must diagnose it.
> This does not convince me, because EPIPE is part of the normal shutdown
> protocol of pipes, when the pipe writer chooses to block or ignore SIGPIPE.
> The very purpose of having different error codes listed in <errno.h> is
> to be able to react differently on them.

Sounds like we should ask the Austin group for an opinion.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


reply via email to

[Prev in Thread] Current Thread [Next in Thread]