RE: slog...

[John Wise]

Hmmmm. There are a number of options all of which may be bad. ;) Create your
own directory at runtime, the current directory where the exe is running, or
some log dir when commonc++ is installed. The last one is what I've seen on
a unix app I'm trying to port. I untarred and there was a log dir. I might
install the log dir off the tree where most of my stuff was installed, but
check for the existence of that dir before I began running, if it didn't
exist, create it, and begin writing. I don't think it really matters as long
as it's well documented. Then if someone complains you can move it or ask,
well what do you suggest. Something else to consider is that if memory
serves, I don't think win32 event logging will work on windows systems other
than win2k or winnt, I think the api calls in the case of 9x write to flat
files anyway.


>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.