Hi Micheal,
>> i have observed a little exceptional (In my opinion) thing, which i
>> don't understand...
>>
>> I have configured my apache (2.0.59) with SVN Modules and configured a
>> CustomLog entry to print out SVN events...so far so good...
>>
>> ...CustomLog configured as described in the SVN Book (for SVN 1.5.x).
>>
>> I can see the operations which are done via Command Line Client or
>> TortoiseSVN...(checkout-or-update etc.)
>>
>> But...i can's see any thing which happen if someone goes via Browser to
>> the URL...? This is more or less equal to svn list ? isn't it ?
>
> One major source of confusion and frustration with the mod_dav_svn
> operational logging support is that it was design to merely complement the
> baseline Apache logging. This means that where no interesting additional
> information would be added with an operational log line, no such line is
> written. Unfortunately, this means that simple GET requests such as those
> used when navigating a repository with a web browser don't generate
> subversion log lines (because they would be entirely redundant with
> access_log lines). I think I was originally in favor with this idea, but
> have since grown to hate it due to the confusion it causes.
Ok...that's a statement...
But do exist plans to change that or do exist design/proposal documents
about that ? May be to get it consistent with svnserve logging output ?
Kind regards
Karl Heinz
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2059040
Received on 2009-05-04 21:07:54 CEST