Should svnserve set umask to 002?

When using ra_svn over ssh, svnserve runs as the user making changes to
the repository. If someone has their umask set to 022 then they might
create files that are not writable by other people in the repository
group. It looks like svnserve and ra_dav die horribly and leave the
repository in an inconsistent state if there is a permission problem:

[Thu Jan 23 11:39:42 2003] [error] [client 10.27.8.134] Could not open
the SVN filesystem at /data/subversion/repository [500, #160029]
[Thu Jan 23 11:39:42 2003] [error] [client 10.27.8.134] (17)File exists:
Berkeley DB error while opening environment for filesystem
/data/subversion/repository/ db:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]

I think perhaps svnserve should explicitly set the umask to 002. Even
better, is it possible to fix svnserve and ra_dav so that they die more
gracefully?

  Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:09:33 2006