Michael Sinz wrote:
> Michael R Sweet wrote:
>>Michael Sinz wrote:
>>>>At least you'd be starting with existing, working code that is
>>>>well-suited to different kinds of logging...
>>>Ahh, but this still does not address the issue of the client code
>>>(svn/etc) doing the logging when the access is via file:// - or maybe
>>>it does with the extra demand that file:// access use must also give
>>>full write access to the log files to all users. (Even if they only
>>>have read access to the repository)
>>Well, a couple thoughts on that:
>> 1. If you want logging with file:// access, you are already
>> setting up permissions properly to provide file:// access,
>> so this isn't a large barrior IMHO.
>> 2. If you care about the security/validity of the log, then
>> you'll likely use svnserve or mod_dav so that users don't
>> need direct access to the log file(s).
>>In short, I don't think write access to log files is a major
>>issue for file:// usage.
> I think you missed the key statement - write access would be needed
> even if read-only access to the repository. But, as you state, if you
No, I didn't miss it. However, by using the Apache logging code
(and in the future a potential APR version of it) you also get
logging via syslog/Windows event log which means you may not need
direct write access to the log files.
In any case, if someone *is* using file:// to access their repos
then I don't know how you can ever provide "accurate" logging since
the repos can be accessed outside of Subversion. The best you can
do is say "for accurate logging you must use either mod_svn or
svnserve without SSH" and explain why file:// and svn+ssh:// may not
be reliable. People that care about accurate logging will use the
right schemes to get there - just provide the ability to log things
(not enabled by default) and let the users decide how best to
configure it on their systems.
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 25 14:48:15 2005