ViewVC logotype

Annotation of /eggdrop1.8/doc/WEIRD-MESSAGES

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph

Revision - (hide annotations) (download) (vendor branch)
Mon Jul 26 21:11:06 2010 UTC (9 years, 11 months ago) by simple
Branch: eggheads, MAIN
CVS Tags: v1, HEAD
Branch point for: gettext
Changes since 1.1: +0 -0 lines
Imported Eggdrop 1.6.20

1 simple 1.1 $Id: WEIRD-MESSAGES,v 1.9 2010/01/03 13:27:22 pseudo Exp $
3     Weird Messages That Get Logged
4     Last revised: March 10, 2003
5     _____________________________________________________________________
7     Weird Messages That Get Logged
10     Shown below are some messages that Eggdrop might log from time to time
11     that may seem a bit strange and have meanings which may not be obvious.
13     (!) timer drift -- spun N minutes
15     This can be caused by one of several reasons.
17     - Your bot could have been swapped out of memory for a while, or for
18     some reason the computer could have stopped letting the bot run. Once
19     a minute, Eggdrop does a few maintenance things, including counting
20     down any active Tcl timers. If for some reason, several minutes pass
21     without Eggdrop being able to do this, it logs this message to let
22     you know what happened. It's generally a bad thing, because it means
23     that the system your bot is on is very busy, and the bot can hardly
24     keep track of the channel very well when it gets swapped out for
25     minutes at a time.
27     - On some systems (at least Linux), if the DNS your bot is using to
28     lookup hostnames is broken and *very* slow in responding (this can
29     occur if the DNS server's uplink doesn't exist), then you will get
30     4-5 minute timer drifts continuously. This can be fixed by loading
31     the dns module.
33     - The clock on your machine has just been changed. It may have been
34     running behind by several minutes and was just corrected.
36     (!) killmember(Nickname) -> nonexistent
37     We have yet to track this down. It's a mildly bad thing, however. It
38     means the bot just got informed by the server that someone left the
39     channel -- but the bot has no record of that person ever being ON the
40     channel.
42     jwilkinson@mail.utexas.edu had some insight into this one:
44     This is not an Eggdrop bug, at least not most of the time. This is a
45     bug in all but perhaps the very latest ircd systems. It's not uncommon
46     during netsplits and other joins for the server to lose track of killed
47     or collided join notices. Also, in some servers, it is possible to
48     specify non-standard characters, such as caret symbols, which get
49     falsely interpreted as capital letters.
51     When converted to lowercase, these symbols fail to get processed, and
52     joins are not reported, although parts are.
54     _____________________________________________________________________
56     Copyright (C) 2003 - 2010 Eggheads Development Team

ViewVC Help
Powered by ViewVC 1.1.23