Re: unexpected rename() behaviour

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Andreas Schwab
Date: Saturday, March 29, 2008 - 5:36 am

Ketil Froyn <ketil@froyn.name> writes:


POSIX explicitly requires that behavior.


I don't think there are many programs that encounter that situation.
Probably in most cases the new file was created by the program and
guaranteed to be different from the old file.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
unexpected rename() behaviour, Ketil Froyn, (Fri Mar 28, 5:07 pm)
Re: unexpected rename() behaviour, J.A. , (Fri Mar 28, 5:16 pm)
Re: unexpected rename() behaviour, Ketil Froyn, (Sat Mar 29, 3:56 am)
Re: unexpected rename() behaviour, Andreas Schwab, (Sat Mar 29, 5:36 am)
Re: unexpected rename() behaviour, David Newall, (Sat Mar 29, 5:57 am)