There's already a logging system in place, but it's somewhat complex. It appears the log system was reworked at some point.
From the Wiki:
Quote:
Log Systems
eqemu is a mess of various logging mechanisms... here is a quick explanation:
There is an "overarching" log system, which logs into the eqemu_* files which is used for about 90% of the logging, but there is no runtime flexibility in this system
the EQDEBUG define is an older mechanism to tune the log messages coming out, but more or less, you want to leave it at its default of 5 (in makefiles/projects)... lower and you miss interesting stuff, higher and you'll log yourself to death.
the 'loglevel' variable is even older, not really used for much anymore, and should prolly be removed completely.
The logsys stuff linked above is the "new" mechanism of logging info, which allows runtime configuration of logging information and is documented at the link above. This system sits on top of the "overarching" log system, putting all of its output through the "debug" facility, and hence into eqemu_*_debug.log
finally, there is a lot of bullshit logging done with printf/cout in the code, which does not go into any of the eqemu_* files, if you use the launcher, it pipes all output (logger or direct) into the zone_* files.
|
I do think there might be some opportunities for the logging system which are definitely worth looking into, especially trying to narrow it down to 1 useful system. In addition, I think it would be a lot easier than reworking the entire logging system again
Threaded Mode
