John Peacock wrote:
> Branko ÄŒibej wrote:
>
>> I think we need to put a pretty hugh priority on stabilizing threaded
>> svnserve, and adding server-side logging. Other problems aside, a
>> server that doesn't produce logs is simply not ready for serious usage.
>
>
> I was actually thinking about giving this a go myself. I want to run
> svnserve under daemontools (actually, I am already doing that, just
> not getting any logs), so I'd be a prime candidate to do this work.
>
> Do I really have to implement a syslog-style interface, or can I just
> add a new commandline switch that spews logs on STDOUT (which is all I
> need)? If the former, I'll have to do the latter anyways.
I think so...stdout wouldn't work under inetd, for example.
> I assume the Win32 interface is going to have to use the Event Log in
> either case.
Oh no! The event log tends to fill up too quickly. Apache logs to a file
on Windows, and I think that would be appropriate for svnserve. I don't
know about log rotation, though; I suspect Apache does its own, because
there's no logrotate daemon on Windows.
I wonder if we couldn't just rip the logging logic out of httpd, and of
course simplify it. And put the configuration in
repo/conf/svnserve.conf, I expect, and also a global config file
(/etc/svn/svnserve?)/
> Anyone want to nominate /how much/ logging happens (comparable to the
> HTTP logging or less chatty)? Do we want
>
> 1) logs
> 2) verbose logs
> 3) really compulsive debugging logs
>
> as seperate levels of logging?
Yes, yes and yes. I'd call that: error, info, and debug. Only errors go
to the error log; all actions, including errors, go to the info log; and
the debug log is for helping reproduce an error and should be turned off
by default.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 18 04:13:15 2004