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 #12
Topic: rename() impact on .. ctime Relevant Sections: 184.108.40.206
In 220.127.116.11 Description [Rename a File], page 100, lines 584-585:
"Upon successful completion, the rename() function shall mark for update the st_ctime and st_mtime fields of the parent directory of each file."
If a directory containing an entry for dot-dot is renamed, is a conforming implementation required to mark for update the st_ctime and st_mtime fields of the renamed directory?
It is unspecified whether the time fields of the directory are updated.
Rationale for Interpretation
It is only the parent(s) of "old" and "new" which are required to be marked for update. It is unspecified whether the directory entry for dot-dot is considered to be file data and, as such, it is unspecified whether it is implementation-defined or unspecified that the time fields of the directory are updated. A better understanding can be obtained by reading POSIX.1-1990 subclause 2.3.5.