From: Eric Goebelbecker (egoebelbecker_at_[hidden])
Date: 2005-05-19 13:30:37
My needs are similar.
1) All messages go to a single file. The ability to filter messages to
different files based on the severity (a la syslog) is a nice to have,
but certainly not critical.
2) The ability to dynamically change what messages are sent.
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. Since the first
thing a client will do when a problems occurs is restart the
app...overwriting the log will not do. Having the startup script move
the log to a new name is a possibility, but less than desirable.
On 19 May 2005 12:45:45 -0500, Robert Zeh <razeh_at_[hidden]> wrote:
> Our current logging is very simple. At start up, most of our
> applications specify a log file, which can be gotten later via a
> singleton. The singleton allows global access to an output stream for
> their logs.
> There are a few things it doesn't do that we'd like in a logging framework:
> 1) Automatic timestamps, which are currently done manually.
> 2) Debug levels, so that some log messages could be ignored
> while others are actually written to the output stream. It
> would be nice if we could specify debug levels as a stream
> manipulator, ie:
> log << debugLevel(5) << " reactor meltdown " << endl;
> If the debug level is below 5, the reactor meltdown message
> is ignored. Sometimes we dynamically adjust the debug
> level, so that we can get more information from a
> misbehaving application.
> Of course, you have to somehow specify when log level is
> being reset. I haven't thought that part through.
> Robert Zeh
> Manager, Applications Development
> Error Free Software
> John Torjo <john.lists_at_[hidden]> writes:
> > Hi all,
> > In order to make the Logging lib as usable as it can be, I'd like to
> > know what is *your* scenario, when using a Logging lib.
> > Thus, I'll do my best to make it as easy as possible to use my lib,
> > and also tweak it to be easily usable in most common scenarios.
> > Even if you scenario fits an already described one, please just reply
> > to that email with something like "mine too!", so that I'll know which
> > scenarios are most common.
> > Thanks!
> > Best,
> > John
> > --
> > John Torjo, Contributing editor, C/C++ Users Journal
> > -- "Win32 GUI Generics" -- generics & GUI do mix, after all
> > -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter)
> > -- http://www.torjo.com/cb/ - Click, Build, Run!
> > _______________________________________________
> > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
> 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