Does using the umask hack adversely affect a non-SSH or inetd svnserve
process? If not, then it wouldn't hurt to use it. If it would affect them,
then I'm not sure what would be done.
Sly
cmpilato@collab.net wrote:
> "Steve Williams" <stevewilliams@kromestudios.com> writes:
>
>> Uhh, yeah... that one. *grin*
>>
>> cmpilato@collab.net wrote:
>>> "Steve Williams" <stevewilliams@kromestudios.com> writes:
>>>
>>>> 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?
>>>
>>> You, uh, mean 'svnserve', right?
>
> Now, to address the actual question. Actually, I have to first ask a
> question -- do all uses of svnserve require the umask hack? My
> understanding was that this was only a problem that only occurs in the
> svn+ssh scenario, and that a non-SSH daemonized or inetd'd svnserve
> process doesn't run into these umask problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 08:09:31 2003