manual: Clarify renameat documentation

Clarify the meaning of renameat arguments.

Reviewed-by: Collin Funk <collin.funk1@gmail.com>
This commit is contained in:
Jitka Obselkova 2025-06-14 11:19:46 +02:00 committed by Florian Weimer
parent 1149b4f64f
commit 53ea6db9fd
1 changed files with 4 additions and 1 deletions

View File

@ -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}.