Intro Info
Frequently Asked Questions
Eggdrop is an IRC bot, written in C. If you don't know what IRC is, this is probably not
whatever you're looking for! Eggdrop, being a bot, sits on a channel and takes protective
measures: to keep the channel from being taken over (in the few ways that anything CAN),
to recognize banished users or sites and reject them, to recognize priveledged users and
let them gain ops, etc.
One of the more unique features of eggdrop is its "party line", accessable via DCC chat, which allows you to talk to other people lag-free. Consider it a multi-way DCC chat, or a miniature IRC (complete with channels). You can link up with other bots and expand the party line until it actually becomes something very much like IRC, in fact. |
|
|
|
We are sorry but crontab use is not allowed by users on this system. Several users have abused this privilage and have tried to compromise this site with it. |
You have two choices, the first is easiest and the second should
only be used if the fist one doesn't work.
Choice number 1:
chmod u+x addpatch then type addpatch file.patch and it will tell you what the last patches installed where and ask if you want to install the patch, if the patch you are installing is listed then press 'n' then enter if it's not then press 'y' and then enter. Choice number 2:
Here is the basic command, ungzip the patch file, and run the following command from your eggdrop directory (not the src directory): patch -p1 < file.patch Once this is complete, execute the following command: find . -name "*.rej" -print If it returns a list with filenames that end in the rej extension then the patch didn't apply properly, ensure that the patch is for the version intended, ensure that you have the original source, and ensure that the patch is not corrupted. If it turns out that the patch was successful then be sure to recompiling by running make again. |
|
Your machine is set up strangely, and eggdrop can't figure out its
network hostname. To fix this add the following command to your
eggdrop.conf (Or whatever you renamed it to) file.
If This does not work try setting an environment In csh or tcsh: It should work after that, or add those above commands to your '.login' file (sh or ksh: '.profile'). |
Tcl is a scripting language written by John Ousterhout. It's much better than most "in-built" script langauges (like the one in ircII) and is meant to be linked with anything needing a script language. So I linked it with eggdrop. The file "tcl-commands.doc" in the eggdrop directory contains a list of the commands added to Tcl by eggdrop. There are also several example scripts in the script/ directory, and there are gobs of scripts floating around on the ftp sites if you like working by example (which is typically the best way). |
There is a Tcl script called "weed" distributed with eggdrop. To use
it, type: It will give you a list of options for weeding out your userlist. You can erase users who haven't been on the channel within a specified number of days, or erase any ops who haven't set a password yet, etc. Lots of options. |
Terminate Signal". What Does That Mean Aand Can I Prevent It? |
There's nothing you can do to prevent it. It means the system admini stator is killing the eggdrop process. Most of the time, it's an automatic thing that happens when the system is being rebooted -- so it's harmless, and if you have a crontab running, the bot will get restarted when the system is back online. Occassionally the system administrator will kill the bot manually -- for example, if he/she doesn't want bots running on the system. |
This happens on Linux machines which have recently been converted to ELF by upgrading to Slackware 3.0. Apparently Slackware 3.0 comes with a non-ELF (a.out) Tcl library, and the compiler doesn't handle that well. (It should give you an error; instead it barfs.) Fixing it is tricky because even if you recompile libtcl.a, the linker will most likely find the "bad" one first, and your work will be in vain. Here's a fix that's been floating around on the eggdrop list:
|
Backdoors I Can Use To Take Their Bot Down? |
No, there have never been any backdoors and there never will be, so please stop asking. Every once in a while, someone finds a way to exploit a bug in eggdrop, but we fix these bugs as soon as I find out about them. If you want to bring down someone else's bot, you will not have my help. |
Modules are a way of adding extra C code from the bot, much like tcl scripts, without requiring the bot recompiling, see doc/MODULES for more info |
Yes, there is a mailing list. The address has changed recently,
though, and (thank the heavens) I don't have to maintain it any more.
To subscribe, send email to:
majordomo@sodre.net
Robey is no longer developing the eggdrop code (although he does put a word in every now and then) so don't bother emailing him. If you have a serious problem, email the eggdrop mailing list and it will get to the coders. |