diff options
| author | наб <nabijaczleweli@nabijaczleweli.xyz> | 2023-04-11 04:21:32 +0200 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2023-04-11 16:55:38 +0200 |
| commit | 74d9f80a0b013aea4e134311d63c3406eae389b8 (patch) | |
| tree | 36ac5022f561bcb7249ee4e80471066399c48d4b | |
| parent | 0a94799e2b19bd3a33d8f4d6a3b7850dee7e41c4 (diff) | |
fts.3: Note fts_open() behaviour with empty strings
This is undocumented in BSD, too, and present in the original SCCS
check-in (5.1 (Berkeley) 12/30/89).
This is very surprising, since in most other cases FTS is rather quite
sane about error reporting, but /any/ empty string in the input vector
blows out the creation entirely.
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
| -rw-r--r-- | man3/fts.3 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/man3/fts.3 b/man3/fts.3 index 66b2fcab3..49a8507e7 100644 --- a/man3/fts.3 +++ b/man3/fts.3 @@ -722,6 +722,17 @@ for any of the errors specified for and .BR malloc (3). .PP +In addition, +.BR fts_open () +may fail and set +.I errno +as follows: +.TP +.B ENOENT +Any element of +.I path_argv +was an empty string. +.PP The function .BR fts_close () may fail and set |