This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

eggy logging level

Old posts that have not been replied to for several years.
Locked
F
Fluxism
Halfop
Posts: 47
Joined: Mon Aug 05, 2002 8:58 am

eggy logging level

Post by Fluxism »

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?
User avatar
Sir_Fz
Revered One
Posts: 3794
Joined: Sun Apr 27, 2003 3:10 pm
Location: Lebanon
Contact:

Post by Sir_Fz »

From the eggdrop.conf:
# 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.
User avatar
De Kus
Revered One
Posts: 1361
Joined: Sun Dec 15, 2002 11:41 am
Location: Germany

Post by De Kus »

if you dont want to enable raw logging, you can simply this srcipt to save a g-line error:

Code: Select all

bind raw - 465 glineerror

proc glineerror {from key arg} {
  putlog "$from will close link for g-line reason: $arg"
  return 0
}
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens...
User avatar
demond
Revered One
Posts: 3073
Joined: Sat Jun 12, 2004 9:58 am
Location: San Francisco, CA
Contact:

Post by demond »

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

this way you'll surely know what has happened
Locked