Re: file perms in the db dir
On 2004-09-20 13:54:19 -0500, Davy Durham wrote:
> On linux I'm setting up a svnserve environment also using websvn for
> viewing from the web. For the difference in users (user svn vs user
> apache) I've just made apache a member of the svn group. So as long as
> all the files in the db dir are group writable and owned by svn
> everything is fine.
> Well, all is well until after many operations it creates a new
> log.000000## file and perms are wrong, and sometimes the new log file is
> owned by apache instead of svn if websvn caused the creation of the log
> My question is in DB_CONFIG can I specify perms that the new file will
> be created with? Or can it be done with sticky bits on the db dir itself?
> I've looked at the sleepycat docs and didn't see anything. And I wasn't
> sure if something in svn was setting the perms itself.
> It'd just like the files to be owned by svn and perms be 664
You should set the sticky bit on the DB directory and make sure all
repository access is with a 002 umask. AFAIK neither BDB nor svn does
anything with its permissions.
Received on Mon Sep 20 21:20:11 2004
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Users