diff options
| author | Andreas Baumann <abaumann@yahoo.com> | 2009-03-04 19:41:37 +0100 |
|---|---|---|
| committer | Andreas Baumann <abaumann@yahoo.com> | 2009-03-04 19:41:37 +0100 |
| commit | 3005ff3d7a17eb3ab47dfc62150e4e7721c18312 (patch) | |
| tree | 3cdf4c542e20271898be9f21491d0b1dd22e0929 /docs | |
| parent | 8a8f2de504279ff80e674cfc5df15a52153afa28 (diff) | |
| download | wolfbones-3005ff3d7a17eb3ab47dfc62150e4e7721c18312.tar.gz wolfbones-3005ff3d7a17eb3ab47dfc62150e4e7721c18312.tar.bz2 | |
had a closer look at libraries, not really good, they solve just half-way. :-(
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/log/README | 19 | ||||
| -rw-r--r-- | docs/log/TODOS | 7 |
2 files changed, 19 insertions, 7 deletions
diff --git a/docs/log/README b/docs/log/README index 2c0de91..0fa8acd 100644 --- a/docs/log/README +++ b/docs/log/README @@ -15,15 +15,21 @@ Problems to address here: - tracing data should not go to neither syslog or event log - there should be some protection against flooding the logs as they are a system-wide scarse resource! +- get the current User SID and log it (so we see in the event log under + which user the service/program was running) +- Register the event source to the registry, also specify where the + category and messaging DLLs are with localized names and format strings. + (they should be especially packaged or even be delivered in source, so + the admin can compile and use them at wish) Other projects: - .NET EventLog class - log4j -- POCOs EventLogChannel -- www.codeproject.com/KB/cpp/logdriver.aspx -- log4cpp -- log4cplus +- POCOs: EventLogChannel.cpp +- www.codeproject.com/KB/cpp/logdriver.aspx +- log4cpp: NTEventLogAppender.cpp +- log4cplus: nteventlogappender.cxx All of them ignore the message resource and classes of same errors with different parameters. Sadly enough also the MS guys themselves (see @@ -33,3 +39,8 @@ to the worse!). The category is usually used for mapping the coarser gained levels of the logging API to the event logger (POCO, log4cpp). IMHO this is better used for something like subsystems or components. + +log4cplus is the only library to handle the current user SID. +log4cplus adds the event source to the registry. + +.NET at least cares to install a dummy message DLL with a %1's in them. diff --git a/docs/log/TODOS b/docs/log/TODOS index bcbeee8..b7b3608 100644 --- a/docs/log/TODOS +++ b/docs/log/TODOS @@ -21,6 +21,7 @@ - the event logger can log binary data (as dumps), this helps to debug things with the right event log DLL most likely, we have to read more about that later. -- there is an Windows Event Log book around which is quite big, find - out if it's still available - + - there is an Windows Event Log book around which is quite big, find + out if it's still available + - the Windows messages files are avaiable (where?), should the standard + messages be used? |