Is it possible to tweak a setting / alter a core file before compiling, to show a greater level of logging information?
A couple of my bots have been glined, yet I can't find out why.. The eggdrop.log file doesnt provide enough information - why doesn't it specifically give the reason for the gline - rather than just be unhelpful and say;
[13:08:53] -ERROR from server- Closing Link: blahblah by wineasy2.se.quakenet.org (G-lined)
I've searched the forums, checked to see if there are any scripts available which perhaps could log as to why etc, all to no avail.. Can this be done? Perhaps if it can't then maybe a future release will log such critical information?
# Logfile flags:
# b - information about bot linking and userfile sharing
# c - commands
# d - misc debug information
# h - raw share traffic
# j - joins, parts, quits, and netsplits on the channel
# k - kicks, bans, and mode changes on the channel
# m - private msgs, notices and ctcps to the bot
# o - misc info, errors, etc (IMPORTANT STUFF)
# p - public text on the channel
# r - raw incoming server traffic
# s - server connects, disconnects, and notices
# t - raw botnet traffic
# v - raw outgoing server traffic
# w - wallops (make sure the bot sets +w in init-server)
# x - file transfers and file-area commands
#
# Note that modes d, h, r, t, and v can fill disk quotas quickly. There are
# also eight user-defined levels (1-8) which can be used by Tcl scripts.
use +rvd logging flags, but beware, your logfile(s) will grow in size rather quickly
+r logs everything your bot receives from the server
+v logs everything your bot sends to the server
+d logs every Tcl script proc triggering, and more