IEEE Standards Interpretation for IEEE Std 1003.1™-1990 IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX®)
Copyright © 2001 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: sysconf Relevant Sections: 126.96.36.199
I would like to request an official binding interpretation of IEEE Std 1003.1-1996 (POSIX.1). This request deals with the return value of the sysconf(int name) function when the value of the system variable selected by "name" is not limited by the implementation. Currently the standard says (188.8.131.52, p. 112, l. 491 ff.): If name is an invalid value, sysconf() shall return -1.
Otherwise, the sysconf() function returns the current variable value on the system. The value returned shall not be more restrictive than the corresponding value described to the application when it was compiled with the implementation's <limits.h> or <unistd.h>
The standard as published does not address the case where the current variable is not limited by <limits.h> or <unistd.h>, as is the case for one or more variables in our implementation. The POSIX.1 committee has, however, added the following sentence to section 184.108.40.206 in the latest (D13.2) version of the POSIX.1a draft: If the value corresponding to name has no limit, the sysconf() function shall return a value of -1 without changing errno. This is how our implementation behaves, and we ask the committee to verify that such an implementation is compliant with the standard.
Permit behaviour as specified in D13.2 of POSIX.1a draft
The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.
Rationale for Interpretation
See interpretation response above. Forwarded to Interpretations group: 4 Jan 1998 Circulated for review: Feb 1 1998 Finalized: March 4 1998