IEEE Standards Interpretations for IEEE Std 1003.2™-1992 IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX®)--Part 2: Shell and Utilities
Copyright © 1996 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 #83
Topic: renice Relevant Clauses: 5.24
The standard, and obsolescent command line forms can result in an ambiguity regarding which synopsis line to use. The command line renice 4 5 6 may be a "new"synopsis invocation, requesting that the processes 4, 5, and 6 be reniced by the default increment, or it may be an obsolescent invocation, requesting that processes 5 and 6 have their nice values set to 4. How should this ambiguity be resolved? I recommend giving priority to the "new"format, i.e. processes 4, 5, and 6 will all have their nice values incremented by the default nice increment.
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