Re: Why get db/current recreated?

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.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 12 19:27:51 2005