Re: need help setting up svn+ssh://
I'm of the opinion that svnadmin should be a wrapper script by default then
in the official distributions. If this umask problem is such a big deal,
why not have svnadmin as a script in the official distribution?
Michael Wood wrote:
> On Thu, Aug 21, 2003 at 08:37:05AM +1000, Steve Williams wrote:
>>> Your wrapper could be:
>>> 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).
> Glad you liked it :)
> The umask just tells things what permission bits not to set on new
> $ cd /tmp
> $ rm -f test
> $ umask 0000
> $ ls -l test
> -rw-rw-rw- 1 michael michael 0 Aug 21 17:14 test
> $ rm test
> $ umask 7777
> $ ls -l test
> ---------- 1 michael michael 0 Aug 21 17:29 test
> This does not mean that a process is unable to set the permission bits
> in the umask. It's just specifies the default permission bits to
> leave unset.
> man umask for more details. Also search for umask in the bash man
>> 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.
> You could rename the real svnserve to svnserve.bin and call the
> wrapper svnserve. Then in the wrapper refer to svnserve.bin.
> Otherwise, if you are using ssh keys with the "command=blah" in
> authorized_keys, then you could just refer to the wrapper (e.g.
> command="svnserve.wrapper -r /blah -t")
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Aug 22 07:48:24 2003
This is an archived mail posted to the Subversion Users