[PATCH COMMITTED] manual: Clarify renameat documentation

Florian Weimer fweimer@redhat.com
Thu Jun 26 12:46:42 GMT 2025


From: Jitka Obselkova <jobselko@redhat.com>

Clarify the meaning of renameat arguments.

Reviewed-by: Collin Funk <collin.funk1@gmail.com>

---
 manual/filesys.texi | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/manual/filesys.texi b/manual/filesys.texi
index f21f218042..e1c7be867e 100644
--- a/manual/filesys.texi
+++ b/manual/filesys.texi
@@ -1940,7 +1940,10 @@ file systems.
 @comment Unaudited and therefore marked AC-Unsafe and AS-Unsafe by default
 @safety{@mtsafe{}@asunsafe{@asucorrupt{}}@acunsafe{@acucorrupt{}}}
 This function is a descriptor-relative version of the @code{rename}
-function above.  @xref{Descriptor-Relative Access}.
+function above.  @xref{Descriptor-Relative Access}.  If @var{oldname} or
+@var{newname} is a relative path, it is interpreted relative to the
+directory associated with @var{oldfiledes} or @var{newfiledes},
+respectively.  Absolute paths are interpreted in the usual way.
 
 Compared to @code{rename}, some additional error conditions can occur.
 @xref{Descriptor-Relative Access}.

base-commit: 1149b4f64fea6e07e84e285981b84c8ccaccb025



More information about the Libc-alpha mailing list