Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001729 |
[1003.1(2016/18)/Issue7+TC2] System Interfaces |
Objection |
Clarification Requested |
2023-05-18 09:30 |
2023-08-17 10:58 |
|
Reporter |
geoffclare |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Applied |
|
|
|
|
Name |
Geoff Clare |
Organization |
The Open Group |
User Reference |
|
Section |
mkdir() |
Page Number |
1317 |
Line Number |
43825-6 |
Interp Status |
--- |
Final Accepted Text |
|
|
Summary |
0001729: mkdir() ENOENT and ENOTDIR overlap |
Description |
For a call such as:mkdir("regular_file/foo", mode) the descriptions of ENOENT and ENOTDIR on the mkdir() page both apply:[ENOENT]A component of the path prefix specified by path does not name an existing directory ... [ENOTDIR]A component of the path prefix names an existing file that is neither a directory nor a symbolic link to a directory. For other file creation functions, e.g. open(), mkfifo(), and fopen(), ENOENT uses "existing file" instead of "existing directory", avoiding this problem.
Also, strictly speaking path does not specify a path prefix (it specifies a complete pathname). Again, other pages don't have this problem, as they refer to "the path prefix of path".
|
Desired Action |
Change:A component of the path prefix specified by path does not name an existing directory to:A component of the path prefix of path does not name an existing file
|
Tags |
applied_after_i8d3, tc3-2008 |
|
Attached Files |
|
|