1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
- local localized error handling (GetLastError and strerror_r strings)
- Windows event logger
- audit event log types, especially the effects on syslog and the upper
abstraction layer
- event log categories, for instance for components, the idea is that
an admin should be able to filter by category.
- some categories could be the wolf_log_level_t's as a first step,
especially because the event logger knows only about 4 levels of
errors
- error ids and classes, but this means they also have to be there
for Unix and the abstraction layer above, so no more
WOLF_LOG( "%s bla bla %d", ... )
things look more like
WOLF_LOG( LOG_COMP_NETWORKER, LOG_NETWORKER_ERROR_455,
_T( "%s bla bla bla %d", ... );
- parameter list dilemma of typed one (classic C) %s, %d versus
positional one in Windows %1 %2
- security identifier if we start to log to the audit log, as long
as we have a simple application log, we should have enough rights
- 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.
links & literature:
- there is an Windows Event Log book around which is quite big
|
