From 5efbb6f6e6e327977505d8aa16ae85b18286d98a Mon Sep 17 00:00:00 2001 From: jilles Date: Sun, 18 Mar 2012 21:46:27 +0000 Subject: fts(3): Mention that FTS_NOCHDIR imposes {PATH_MAX} limits on the returned pathnames. With the current API (no *at functions), FTS_NOCHDIR requires that the fts_accpath start with the original path passed to fts_open(); therefore, the depth that can be reached is limited by the {PATH_MAX} constraint on this pathname. MFC after: 1 week --- lib/libc/gen/fts.3 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/libc/gen/fts.3 b/lib/libc/gen/fts.3 index d34b61b..193e60e 100644 --- a/lib/libc/gen/fts.3 +++ b/lib/libc/gen/fts.3 @@ -419,14 +419,17 @@ be provided to the .Fn fts_open function. .It Dv FTS_NOCHDIR -As a performance optimization, the +To allow descending to arbitrary depths +(independent of +.Brq Dv PATH_MAX ) +and improve performance, the .Nm functions change directories as they walk the file hierarchy. This has the side-effect that an application cannot rely on being in any particular directory during the traversal. The .Dv FTS_NOCHDIR -option turns off this optimization, and the +option turns off this feature, and the .Nm functions will not change the current directory. Note that applications should not themselves change their current directory -- cgit v1.1