Re: slog...

[David Sugar]

Assuming it writes a log file, where should this log file be written?  The 
purpose of slog is essentially to serve as a C++ wrapper for syslog() type 
logging.  In syslog, on posix systems, logging messages are categorized by 
facility and severity, and then an external deamon processes the requests and 
can either stream them to a log file or even do other things (such as 
syslog-ng supports) based on the message content.  For example, a critical 
alert could be tied to something that then beeps your pager. However, even 
logging directly to a single file would be useful.

John Wise wrote:

> If the OS dies, which Winxx never does ;) it would be hard to get
> information from the event log, whereas a simple file might be easier to get
> to, clean up, move around, so I'd vote for a file. Also a file log writer
> could be written to be OS independent, something that wrote to the win32
> event log would not. But I've barely looked at the code, in fact just a bit
> of the socket stuff, so I don't know what kind of events you want log. 
>
>
>
> Anyway my 2 cents.
>
>
>
> John Wise
>
> Peregrine Systems, Inc.
>
> Product Developer
>
> address@hidden
>
>
>
>
>
>
>
>
>
>
> > I think it is time to decide on some kind of slog implimentation for the
>
> win32 
>
>
> > target.  Should slog somehow connect to the win32 "event logger" or should
>
> it 
>
>
> > generate a log file completely on it's own??
>
>
>
>
> > David
>
>
>
>
>
>
> _______________________________________________
>
> Bug-commoncpp mailing list
>
> address@hidden
>
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp