On Jun 13, 2007, at 11:58, Jeremy Freeman wrote:
> I am having some trouble with umask and/or permissions it would
> seem. Every so often database recovery is required because a log
> file does not have g+w permissions. What is puzzling to me is I
> have svnserve, svnlook, svn, and svnadmin commands wrapped with a
> shell script like the following for svnserve:
>
>
>
> #!/bin/sh
>
> umask 002
>
> exec /usr/bin/svnserve.real "$@"
>
>
>
> But I am periodically still getting log files owned by root and not
> g+w.
>
>
>
> -rw-rw-r-- 1 jlong svn 1048510 Jun 12 19:39 log.0000000658
>
> -rw-r--r-- 1 root svn 1514 Jun 12 19:39 log.0000000659
>
>
>
> Running version 1.1.4
>
>
>
> What am I missing here?
I don't know why you're having that problem or how to solve it. But I
can say that you should update to Subversion 1.4.4, which should
include many many bug fixes over what you have in 1.1.4. Also, since
1.2.0, BDB is no longer the default; FSFS now is. With FSFS, you
cannot experience BDB errors like this. So, one way to work around
the problem would be to convert your BDB repository to FSFS.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 15 07:56:50 2007