egghelp/eggheads community

tcl error in script for..

2003-01-12T11:15:29-04:00

ok, after some narrowing down.. i think i've found the tcl.

it seems to be gozzip's channel protection. i'll try to get in touch with him, but if anyone wants to take a look at the tcl.. just send me a message and i'll e-mail it.

for now, au revoir.

..and thanks for aaall the help!

//chasm

Statistics: Posted by chasm — Sun Jan 12, 2003 11:15 am

tcl error in script for..

2003-01-12T10:35:43-04:00

ah, ok. well, i tried without also.. but now, i've done this:

i searched for 'uhost' within the scripts folder and searched for 'unset' within these files. i'm currently using these tcls that use the 'unset' command:

bseen // bass's seen script. v1.4.2c
moretools // mc_8's more tools v3.0.4
chanpro // gozzip's channel protection 1.1
banflooders // mc_8's ban flooders 2.1
topic_resynch // mc_8's topic_resynch 2.1
chanpeak // dawg's chanpeak 1.3
dccwatch // dr. nibble's dccwatch 1.0.4
norepeats // strikelight's norepeats 1.2

should i search for 'unset: $uhost' or 'unset: uhost' just within these files maybe?

//chasm

Statistics: Posted by chasm — Sun Jan 12, 2003 10:35 am

tcl error in script for..

2003-01-12T10:26:31-04:00

Windows search doesn't allow wildcards within this box.

Statistics: Posted by ppslim — Sun Jan 12, 2003 10:26 am

tcl error in script for..

2003-01-12T10:16:50-04:00

hmm.

now i've tried every possible search-method using wildcards to find anything that matches 'unset uhost', but it looks rather hidden from mr. searchengine too.

there was no hit with 'unset uhost', 'unset*uhost' and all the other methods. i find alof of hits with 'uhost' and 'unset' (of course), but none that match 'unset uhost' etc.

i have done all my searches without the ' chars, yeah. hmpf.

grep for windows == sucks.

//chasm

Statistics: Posted by chasm — Sun Jan 12, 2003 10:16 am

tcl error in script for..

2003-01-12T09:54:02-04:00

Click "start" and navigated to "find files and folders".

Simply type "unset uhost" in the sectond text box.

Select borwser, and navigate to the windrops scripts directory, to speed things up.

Now do yoru search.

Statistics: Posted by ppslim — Sun Jan 12, 2003 9:54 am

tcl error in script for..

2003-01-12T09:54:03-04:00

what if it's a windrop?

//chasm

edited: i found 'grep for windows'. trying it out now.

Statistics: Posted by chasm — Sun Jan 12, 2003 9:49 am

tcl error in script for..

2003-01-12T09:48:00-04:00

OK - go to your shell, and change to the bots script directory.

Note type the following

grep "unset \uhost" ./*

This should locate which script this is in.

Now paste the name fo the script, and where you can obtain it from (or upload a copy to some web-space, for use ot see, if it's not in the usual places).

We should be able to help a little more from there.

Statistics: Posted by ppslim — Sun Jan 12, 2003 9:48 am

tcl error in script for..

2003-01-12T09:38:30-04:00

hi again.

finally(?) i got an error. it's been a long while since last time, but now i have a new example with rename.tcl installed:

[14:31] Timer error: unset : can't read "uhost": no such variable

does this help?

//chasm

Statistics: Posted by chasm — Sun Jan 12, 2003 9:38 am

tcl error in script for..

2003-01-10T06:37:57-04:00

i upgraded from version 1.6.12 to 1.6.13, so it is currently running the newest version.

sadly, i got an error about 1½ hour ago. i've restartet the bot with rename.tcl and test.tcl, so i'm waiting for the next one.

//chasm

Statistics: Posted by chasm — Fri Jan 10, 2003 6:37 am

tcl error in script for..

2003-01-10T06:31:14-04:00

Out of interest, what version where you running previously.

It may be that it was that old, that needed commands where not provided.

Statistics: Posted by ppslim — Fri Jan 10, 2003 6:31 am

tcl error in script for..

2003-01-10T04:06:10-04:00

i sorted this one out too. i installed a new version of the drop and just moved all the important files over.

for now, its seems like it did the trick. no errors for 20 hours.

i'll get back to you when its been running for a couple of days.

thanks for all the help and suggestions!

//chasm

Statistics: Posted by chasm — Fri Jan 10, 2003 4:06 am

tcl error in script for..

2003-01-08T11:19:54-04:00

As stated originaly, the script si pretty basic, and doesn't take any consideration for possible issues like this.

The script works by renaming the timer commands. When a timer is needed, the script adds information, that can be used to debug it later.

When you rehash, the script will try renaming the command again.

The issue is this second rehash.

Once the bot is loaded, there should be no need to rehash. The script is designed for use during debugging periods (like this) only, and isn't designed to be used as a everyday script fixer (As it doesn't fix scripts).

If you load the bot without the rename.tcl loaded, and there are no more of these timer errors, then the problems have vanished.

It could take days for them to occur, but I sugest you keep rename.tcl loaded, and do not do a rehash.

Statistics: Posted by ppslim — Wed Jan 08, 2003 11:19 am

tcl error in script for..

2003-01-08T10:12:21-04:00

hah, oh my. this -is- funny. i tried to rehash the bot and then..

(read error: eof from client)

i didn't even get to see what the error message was. i tried to start up normally and there was no error. as soon as i rehash, blooop.

hah.

//chasm

i tried to unload the rename.tcl script and it rehashed perfectly.

//chasm

Statistics: Posted by chasm — Wed Jan 08, 2003 10:12 am

tcl error in script for..

2003-01-08T10:08:45-04:00

hah, oh my. this -is- funny. i tried to rehash the bot and then..

(read error: eof from client)

i didn't even get to see what the error message was. i tried to start up normally and there was no error. as soon as i rehash, blooop.

hah.

//chasm

Statistics: Posted by chasm — Wed Jan 08, 2003 10:08 am

tcl error in script for..

2003-01-08T10:02:48-04:00

anyways, i don't see any errors yet. this is promising.

//chasm

nvm. Let's hope it stays without errors

Statistics: Posted by egghead — Wed Jan 08, 2003 10:02 am