rename.2: Clarify that ERRORS may cause rename to fail (not to be nonatomic)

The existing wording suggests that there are ERRORS that may cause
the operation to be nonatomic. The point is of course that there
are various restrictions on rename operations that may cause the
operation to fail.

Reported-by: Tim Savannah <kata198@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-09-04 03:53:28 +12:00
parent cbac502be2
commit ae01f2b58b
1 changed files with 4 additions and 2 deletions

View File

@ -79,10 +79,12 @@ Open file descriptors for
.I oldpath
are also unaffected.
Various restrictions determine whether or not the rename operation succeeds:
see ERRORS below.
If
.I newpath
already exists, it will be atomically replaced (subject to
a few conditions; see ERRORS below), so that there is
already exists, it will be atomically replaced, so that there is
no point at which another process attempting to access
.I newpath
will find it missing.