John Peacock wrote:
> Molle Bestefich wrote:
>> Do what everybody else does and output errors and warnings to:
>>
>> - Syslog if running on Unix
>
> This is a slight exaggeration, since Apache (for example) has it's own logging
> subsystem and doesn't use Syslog at all (though I think you can make it use
> syslog if you want). AFAIK, this is due to the known issues with classical
> syslog's behavior under extreme load.
File a bug against syslog-ng =)
>> - Eventlog if running on Windows (cmon, it's like 1-2 lines of code & it
>> makes you instantly compatible with what everybody else does)
>
> Eventlog has it's own problems (like not including file rotation, so the log
> file can fill up).
The NT eventlog is very versatile, and there's a million tools out
there that will rotate, twist and turn and optionally suck every event
out of it and produce a neat report for you. For every day use, you
can right-click a log in the viewer and choose "overwrite events as
needed", "overwrite old events", "don't overwrite". If you want to
rotate the log, schedule a script that does this using eg. AT.
Example log rotate script here (2nd example):
http://gethelp.devx.com/techtips/nt_pro/10_minute_solutions/10minNT0201-2.asp
There's a bunch of other sites that carry examples - it's basic WMI 101.
> There is no reason to limit _this_ project to a single logging scheme. If the
> logging subsystem is pluggable, then it can support all of these schemes without
> bias towards any.
Sounds very reasonable.
Can't say I'd vote for stdout being the default on any system though :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 19:12:40 2005