From: Eric Goebelbecker (egoebelbecker_at_[hidden])
Date: 2005-05-19 18:36:00
On 5/19/05, Allan Wind <allan_wind_at_[hidden]> wrote:
> On 2005-05-19T14:30:37-0400, Eric Goebelbecker wrote:
> > 3) Log "rolling" is critical. In a "normal" runtime scenario very few
> > messages are sent to the log - but when something does go wrong a
> > history of "aw shucks" messages can be very helpful.
> * Roll on date and/or size (i.e. roll every 24 hours unless
> the log file hits 2 GB in which case you want to roll now).
> * Log file name contain timestamp of when it was rolled.
> * User-defined action when we roll. Removal of old log files
> either by age, total size, and/or number of files.
> * Log to syslog
I figure that's platform dependent (at least until there's a cross
platform sockets library.) I was planning on writing an appender for
> * Run-time configuration. For instance, log normal stuff to syslog
> but for debugging we want to write trace data to /tmp/debug.log
> for some tags (suggested earlier I think).
> BodyID:11579021.2.n.logpart (stored separately)
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- "Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration." - Stan Kelly-Bootle ------------------------------------ Eric Goebelbecker eric_at_[hidden] http://eric.ominor.net
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk