|
|
|
 |
 |
 |
 |
|
 |
 |
|
 |
 |
|
 |
|
| Development::Development Forum for development topics and for those interested in EQEMu development. (Not a support forum) |
 |
|
 |

08-14-2008, 12:50 AM
|
|
Developer
|
|
Join Date: Mar 2007
Location: Ohio
Posts: 648
|
|
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 
|
 |
|
 |
 |
|
 |

08-14-2008, 01:00 AM
|
 |
Developer
|
|
Join Date: Aug 2006
Location: USA
Posts: 5,946
|
|
Ya, I agree that it seems like there may still be some old stuff left in there that shouldn't be. I guess that would be part of the clean up.
I am aware that there used to be a logging system where you could adjust it from the variables table (loglevel). But, from all I have heard, the only way to currently adjust what is and is not logged is to manually go into the source and comment out the log lines 1 by 1 and then recompile the source. IMO, that is a bit extreme. I also think that logging as it currently is has so much output that I very rarely even look at it. I would much prefer to just completely disable it and only turn it on if I find a problem.
To simplify the rule, it could even be changed to Boolean and just enable or disable logs completely. If the #rule reload command (or whatever the command is) works now, you could possibly even enable and disable logging on the fly without even restarting the server. IMO, that would be awesome and actually make logs useful.
|
 |
|
 |

08-14-2008, 02:08 AM
|
 |
The PEQ Dude
|
|
Join Date: Apr 2003
Location: -
Posts: 1,988
|
|
log.ini is how the current system is configured and works fine, I use it on TGC. There is no need to change any code or recompile. http://www.eqemulator.net/wiki/wikka...a=ServerLogSys
The categories and types in common/logtypes.h are current and all seem to work, at least I have yet to find any one which has not worked yet.
Edit above: I do remember one of the spell types causing a zone crash because for whatever reason it was unable to write out to the log. Wildcard confirmed this issue at the time, but we just disabled that particular type (can't remember which it was) and moved on.
Last edited by cavedude; 08-14-2008 at 10:12 AM..
|

08-14-2008, 09:26 AM
|
|
Discordant
|
|
Join Date: May 2005
Location: Smith Falls, Ontario, Canada
Posts: 283
|
|
Quote:
Originally Posted by cavedude
log.ini is how the current system is configured and works fine, I use it on TGC. There is no need to change any code or recompile. http://www.eqemulator.net/wiki/wikka...a=ServerLogSys
The categories and types in common/logtypes.h are current and all seem to work, at least I have yet to find any one which has not worked yet.
Edit above: I do remember one of the spell types causing a zone crash because for whatever reason it was unable to write out to the log. Wildcard confirmed this issue at the time, but we just disabled that particular type (can't remember which it was) and moved on.
|
log.ini works as intended and does a fine job of showing everything thats needed. I use it as well on my server.
__________________
Rojadruid
Innoruuk Server [legit]
Server Admin.
Server Status: UP
|

08-14-2008, 07:06 PM
|
 |
Developer
|
|
Join Date: Aug 2006
Location: USA
Posts: 5,946
|
|
Thanks guys lol. That saves me alot of work then. Last time I was asking about logged (maybe 6 months ago), I was told by multiple people who have been members for a long time that the current logging system could only be adjusted by commenting out lines in the source.
If I had known that the log.ini actually worked properly, I would have been using it long ago lol.
Thanks
|
| Thread Tools |
|
|
| Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -4. The time now is 06:14 AM.
|
|
 |
|
 |
|
|
|
 |
|
 |
|
 |