[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: Andreas Schwab
Subject: Re: tee logs no output if stdout is closed
Date: Fri, 04 Jul 2008 11:46:34 +0200
User-agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.2 (gnu/linux)

Phillip Susi <address@hidden> writes:

> Andreas Schwab wrote:
>> It would match the behaviour as defined by ASYNCHRONOUS EVENTS in 1.11
>> Utility Description Defaults.
> Could you quote that section or give me a url to somewhere I can see it
> myself?  I have no idea what it says nor where to look it up.



      The ASYNCHRONOUS EVENTS section lists how the utility reacts to
      such events as signals and what signals are caught.

      Default Behavior: When this section is listed as "Default.", or it
      refers to "the standard action for all other signals; see Utility
      Description Defaults " it means that the action taken as a result
      of the signal shall be one of the following:

      1. The action shall be that inherited from the parent according to
         the rules of inheritance of signal actions defined in the
         System Interfaces volume of IEEE Std 1003.1-2001.

      2. When no action has been taken to change the default, the
         default action shall be that specified by the System Interfaces
         volume of IEEE Std 1003.1-2001.

      3. The result of the utility's execution is as if default actions
         had been taken.

    A utility is permitted to catch a signal, perform some additional
    processing (such as deleting temporary files), restore the default
    signal action (or action inherited from the parent process), and
    resignal itself."

> Also what about the issue where tee will try to write() to the now broken
> fd and fail?

That's a normal failure mode.


Andreas Schwab, SuSE Labs, address@hidden
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."

reply via email to

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