Brian W. Fitzpatrick wrote:
>
> On Jul 15, 2005, at 12:45 AM, C. Michael Pilato wrote:
>
>> "Brian W. Fitzpatrick" <fitz@collab.net> writes:
>>
>>
>>> On Jul 14, 2005, at 11:59 PM, Greg Hudson wrote:
>>>
>>>
>>>> The only thing I noticed was some apr_file_t * parameters. We always
>>>> wind up wishing we used svn_stream_t *s when we do that.
>>>>
>>>> I'll also reiterate the point that repository-level logging can't
>>>> capture events which don't involve a repository, such as a client
>>>> trying
>>>> to connect to a URL which doesn't successfully map to a repository.
>>>>
>>>
>>> HTTPd could log that to the error log, but where would svnserve log
>>> those errors to? If we had a global log, where would its conf be?
>>>
>>
>> /etc/subversion ? We already look there for runtime configstuffs
>> (level 1, overridden by ~/.subversion, overridden by programmatic
>> arguments).
>
>
> I suppose, but I thought that was only used by clients?
Currently yes, but there's no reason why servers shouldn't read config
from /etc/subversion (though not from ~/.subversion, obviously :)
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 09:25:42 2005