>> (Also, a future warning: because a bunch of users will be
>> reading/writing the berkeley-db repository files, be careful about
>> permissions and umasks. Many people make the 'svnserve' process on
>> the server into a wrapper-script which 1) sets a sane umask, 2) runs
>> the real svnserve.)
> [snip]
>
> Yes. To be slightly more explicit about this, all users need *write*
> access to the Berkeley DB files even for apparently readonly
> operations. If one user runs some svn command with the wrong umask,
> it will cause problems for other people.
>
> Your wrapper could be:
> #!/bin/sh
> umask 0007
> exec /path/to/real/svnserve "$@"
>
> As long as everyone is in the same group.
This has been the single most helpful response to this issue that I have
seen. I love seeing examples, but it often seems to be assumed that
everyone is a Linux expert and knows exactly what to do to create a wrapper
script that sets the umask (I don't even know what the umask does).
Another question related to this: do we call the wrapper script 'svnserve'
as well? If so, how do we make sure the wrapper script is executed instead
of the real svnserve? Yes I'm a Linux newbie.
Sly
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 21 00:37:53 2003