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™-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 #57
ENAMETOOLONG Relevant Sections: 2.4

Can a pathname be shortened by normal pathname resolution prior to checking for ENAMETOOLONG?

X/Open proposes that it does not. It is our opinion that POSIX.1-1990 requires the ENAMETOOLONG error when the length of a pathname argument exceeds {PATH_MAX}. It says nothing about the length "after pathname resolution", but refers explicitly to the contents of the argument. (X/OPEN)

Interpretation Response

Rationale for Interpretation
The [ENAMETOOLONG] error condition refers to pathname arguments supplied to the implementation, not to any pathnames that might be internally generated by the implementation.