Re: Why get db/current recreated?
Gavin Lambert schrieb am Tue 13. Dec, 11:22 (+1300):
> Quoth Jörg Sommer <mailto:email@example.com>:
> > I run an open SVN repository on a multiuser system. I believe
> > I closed all (but one) ways anyone can mangle the repository.
> > 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/.
> Just use a server process and make the repository only writable by the
> user that the server is running as. And don't use file:// URLs any
That was not the question. I know this, but I can't run a process on this
machine, because it is not 24/7 running. And I'm a simple user. I can't
start processes after boot without login in there.
Die meisten Menschen wollen lieber durch Lob ruiniert
als durch Kritik gerettet werden.
Received on Tue Dec 13 02:53:26 2005
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Users