This is a discussion on Re: [sort of OT] Re: postfix + ocfs within the mailing.postfix.users forums, part of the Mail Servers and Related category; Alex van den Bogaerdt: > On Wed, Feb 04, 2004 at 11:34:46AM -0500, Wietse Venema wrote: > > &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Alex van den Bogaerdt:
> On Wed, Feb 04, 2004 at 11:34:46AM -0500, Wietse Venema wrote: > > > Rename() is destructive. If the target exists, then you > > silently lose mail. > > > > Another reason is that ext2fs could lose files after rename(), > > in violation with the rename() definition. > > Ack, something not easely found in documentation unless you > know where to find it. It is _not_ in (my copy of) the rename(2) > doc! Wietse Solaris: If the link named by new exists, the file's link count becomes zero when it is removed, and no process has the file open, then the space occupied by the file will be freed and the file will no longer be accessible. If one or more processes have the file open when the last link is removed, the link will be removed before rename() returns, but the removal of the file contents will be postponed until all references to the file have been closed. Linux: If newpath already exists it will be atomically replaced (subject to a few conditions - see ERRORS below), so that there is no point at which another process attempting to access newpath will find it missing. FreeBSD: Rename() causes the link named from to be renamed as to. If to exists, it is first removed. |