Re: Svnserve still exiting randomly in threaded mode

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 assume the Win32 interface is
going to have to use the Event Log in either case.

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?

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org