Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

IEEE Standards Interpretation for IEEE Std 1003.1™-2001 IEEE Standard Standard for Information Technology -- Portable Operating System Interface (POSIX®)

Copyright © 2006 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.

Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.

IEEE Standards Department Copyrights and Permissions 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA

Interpretation Request #106
Topic: nohup OUTPUT FILES contradicts DESCRIPTION Relevant Sections: XCU nohup

nohup's OUTPUT FILES section disagrees with its DESCRIPTION.

The DESCRIPTION says that standard error is redirected only if it is a terminal. The OUTPUT FILES says that standard error is also redirected if standard output is a terminal.

Also, the OUTPUT FILES section says output is sent to nohup.out, but the DESCRIPTION says it might be sent to $HOME/nohup.out.

This appears to be an editorial error in the OUTPUT FILES section.

Also please see my earlier defect reports of today {20050713a}, {20050713b}, which may affect the resolution of this defect report.

Change XCU page 676 lines 26185-26188 from:

If the standard input is a terminal, all output written by the named utility to the standard output and error output is appended to the file nohup.out, which is created if it does not already exist.


Output written by the named utility is appended to the file nohup.out (or $HOME/nohup.out), if the conditions listed under DESCRIPTION hold.

Interpretation Response
The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale for Interpretation