[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why get db/current recreated?

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-12-13 19:20:32 CET

On 12/12/05, Jörg Sommer <joerg@alea.gnuu.de> wrote:

> Isn't this archived by the write-lock file? Or do you mean the case
> someone writes and someone reads the file? Can't you use a system lock
> (F_LOCK) call to prevent this situation? What happens if I symlink the
> current file to somewhere else? Does svn follow this symlink and modify
> there the files?

The write-lock file does little to help you if the machine crashes
part way through modifying the current file. An atomic replace is the
safest way to update it, and that's why we do it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 13 20:19:22 2005

This is an archived mail posted to the Subversion Users mailing list.