Y2K problem on eggdrop 1.6.4 ?

[Leonhart]

Command typed on 25th Nov 2001 :-
.tcl unixtime
Tcl: 100665894
.tcl clock format 100665894
Tcl: Sun Mar 11 08:44:54 SST 1973

Server was set at the correct time before doing this. Sorry I can't upgrade my eggdrop to 1.6.5 & above because one of my script couldn't work properly unless you are willing to help me with it. It can't detect handles on quit :
Sweet! We are back to the 70's =)

[Petersen]

Tis the billion second bug. You wanna fix it, you gotta upgrade.

[Yourname]

It isnt such a tedious job to upgrade! Moreover, The TCL programming forum is for asking help on scripts. So why dont you upgrade and also ask for help about that script of yours which isnt compatible with the later eggdrops.

[ppslim]

add

Code: Select all

proc unixtime {} {
  return [clock seconds]
}

to the bottom of your config file, this will provide a workaround for the seconds problem.

[Leonhart]

Thanks a lot ppslim, it works like a charm!
I prefer not to upgrade because I don't want to lose my bot's uptime

Online for 90 days, 22:12 (background) CPU 153:10 cache hit 8.0%

this uptime brings me to another question, what are those CPU & cache hit thingy? What are they trying to show there?

<font size=-1>[ This Message was edited by: Leonhart on 2001-11-25 19:38 ]</font>

[ppslim]

Too be honest, I aint got a clue about the cache, but the CPU is used to show how much of the uptime, is used making calls to the CPU.

Yours works out to be about 4mins 13secs of CPU per hour of uptime.

[Leonhart]

Hmm... that CPU value is very big compare with the other eggdrops that i have. ( one of them only goes CPU 00:13 )
Is it a good sign or a bad omen?

[ppslim]

The value is cumulative, and shows the usage over the whole uptime of the bot.

4 mins an hour is rather good. I have been having problems with 25 mins of CPU an hour.

My lowest is 2 mins, so you are on a role there.

[EcoSpliff]

Hit the computer repetativly and swear!