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 #54
Topic: lockf() threads vs processes Relevant Sections: XSH lockf() Page: 715 Line: 23647

The lockf() man page is currently demanding contradicting behavior. Locking is supposed to have effect on thread or process level. The later is existing practice, only threads from different processes exclude each other. Threads from the same process do not. Therefore the man page must be changed in one place to make the transition from the original wording complete.

Line 23647. Change Calls to lockf() from other threads which attempt to lock the locked file section [...] to Calls to lockf() from threads in other processes which attempt to lock the locked file section [...]

Interpretation Response #54
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