egghelp/eggheads community

I did. Can you test it out and let me know if the changes cause your bot to not flood off?

I'm going to commit a patch to Eggdrop1.6.20 (the CVS version) which changes the queue that a bunch of the JOIN commands use. They are currently using the quickest of the 3 queues (DP_MODE) and should really be using DP_SERVER in most of those cases. See http://www.eggheads.org/devel/ on getting inf...

Very minor issue which I talked about on eggheads@eggheads.org.

Edit src/main.c and change the egg_numver line from 1061800 to 1061900, tar it up again and you have your fixed 1.6.19 release. I could be tempted to release a 1.6.19.1 -- I'll see, we've never done it before.

So I don't have to repeat myself: http://www.eggheads.org/news/2006/04/03/32

You don't update your bot.

Simple as that.

Jeff

Make the startup script start up the bot using "su".

su eggdropuser -c "eggdrop eggdrop.conf"

not that I know of -- 1.6.15 has bugs but none of them are security ones as far as I know.

netupdate isn't binary safe. I don't think it was intended to transfer binary files.

I wouldn't put $botnick into a bind -- since if your botnick changes, the bind will not. I'd use a pubm instead and check the first argument for being your bot's current nick.

rehashing doesn't get rid of old tcl scripts. a .restart will however, since this restarts the Tcl interp.

can't seem to coexist how? I haven't heard of any reports.

Without a GUID (Globally Unique Idenitifer) this is almost impossible to do with the current uptime protocol. For this exact reason, I'm planning to revise the protocol (a version 2) that will deal with these types of issues.

edit the source luke!

Let's donate it to eggheads.org to buy a new server! :)

For $1 billion I'll change it to trustworthy! j/k