Dcc ...

[lsn]

am primit asta in DCC

[14:30:04] <lyncs> [14:30] (!) timer drift -- spun 5 minutes

si nu stiu ce e, ce timer e ala ca nu am in scripturi asa ceva (folosesc scripturile vechi a&a)

[UniversaliA]

Nu-i ajunge timp de procesor la eggdrop. Un proces (prosese) pe shell sau unde e egg-ul, folsoeste toate resursele la procesor & eggdrop-ul iti scrie asta, adica unele prosese (la eggdrop) sunt omise.

[Kurupt]

sau s-a modificat ora le shell (s-a dat cu 5 minute inainte ceasul)

[lsn]

e windrop, la mine pe calc si ai dreptate am modificat ora

[DarkEngel]

Uite si asta - E din doc/html/app-weird.html:

Shown below are some messages that Eggdrop might log from time to time that may seem a bit strange and have meanings which may not be obvious

(!) timer drift -- spun N minutes

This is caused by one of several known things...

Your bot could have been swapped out of memory for a while, or for some reason the computer could have stopped letting the bot run. Once a minute, Eggdrop does a few maintenance things, including counting down any active Tcl timers. If for some reason, several minutes pass without Eggdrop being able to do this, it logs this message to let you know what happened. It's generally a bad thing, because it means that the system your bot is on is very busy, and the bot can hardly keep track of the channel very well when it gets swapped out for minutes at a time.

On some systems (at least Linux), if the DNS your bot is using to lookup hostnames is broken and *very* slow in responding (this can occur if the DNS server's uplink doesn't exist), then you will get 4-5 minute timer drifts continuously. This can be fixed by loading the dns module.

The clock on your machine has just been changed. It may have been running behind by several minutes and was just corrected.