[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: Jörg Sommer <joerg_at_alea.gnuu.de>
Date: 2005-12-13 01:23:13 CET

Hello Garrett,

Garrett Rooney schrieb am Mon 12. Dec, 10:24 (-0800):
> On 12/12/05, Jörg Sommer <joerg@alea.gnuu.de> wrote:
> > The file db/current is recreated (I suppose create db/foo; write db/foo;
> > rm db/current; mv db/foo db/current) everytime a commit happens. This
> > leaves a hole in my system. Anyone could rename or delete files in db/,
> > because I must leave db world-writable. If access to this file would
> > happen "inplace" I could make the directory world-readable and noone
> > could mange the contents of db/.
> Sorry, changes to that file have to be via a replace so that they are
> atomic, otherwise you could try to read the file and get part of an
> update to it.

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?

Thanks for your answer, Jörg.

"Science is the game we play with God to find out what His rules are."

  • application/pgp-signature attachment: stored
Received on Tue Dec 13 02:56:12 2005

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