Help Eggheads.org with infrastructure costs. By donating, you help keep Eggdrop development possible.
Frequently Asked Questions
- What do I do if I get the Error "User file not found"?
- My Eggdrop won't run; It just says "Can't find your hostname!"
- What the heck is Tcl?
- My bot dies, and the last entry in the logfile is "Received terminate signal". What does that mean, and can I prevent it?
- Someone else set up a bot I don't like. Are there any backdoors I can use to take their bot down?
- What are modules?
- Can I compile Eggdrop without dynamic modules?
- Where can I get a pre-compiled Eggdrop for my computer?
- I get "Makefile:3 : invalid operator" of some such thing When I try to "make"
- When I "tclsh scripts/weed <userfile> c" It barfs chunks at me and dies.
- I get "ld-elf.so.1: Shared object "libtcl80.so.1" not found" or "eggdrop: error in loading shared libraries / libtcl8.1.so: cannot open shared object file: No such file or directory" when I try to start my bot.
- I get a whole pile of "unresolved symbol 'Tcl_AppendResult'" (or some other symbol) when I try to load a module.
- Run Eggdrop with the "-m" option (i.e. "eggdrop -m eggdrop.conf").
- Go to IRC and send "hello" to your bot (i.e. "/msg mybot hello").
- You will become an owner on your bot. You can leave the bot running (nobody else will become an owner if they say "hello"), but in the future, don't use the "-m" option when running the bot.
Your machine is set up strangely, and Eggdrop can't figure out its network hostname. You can get around this by setting the my-ip setting in the config file correctly.
Tcl is a scripting language written by John Ousterhout. It's much better than most "built-in" script languages (like the one in ircII) and is meant to be linked with anything needing a scripting language, so I linked it with Eggdrop. Eggdrop Tcl Commands contains a list of additional Tcl commands provided by Eggdrop. There are also several example scripts in the scripts/ directory, and one in the doc directory called first_script.txt. There are also hundreds of scripts floating around on the ftp/web sites if you like working by example (which is typically the best way).
There's nothing you can do to prevent it. It means the system administrator 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. If you have a crontab running, the bot will get restarted when the system is back online. Occasionally, the system administrator will kill the bot manually. For example, if he/she doesn't want bots running on the system.
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 we find out about them. If you want to bring down someone else's bot, you will not have my/our help.
Modules are a way of adding extra features to the bot, much like Tcl scripts, without requiring the bot to be recompiled. See doc/MODULES for more info.
Yes, you can. If the configure script detects that your system CAN'T run modules, it will setup 'make' to link the modules in statically for you. You can choose this option yourself by using 'make static'. You can also try to compile dynamic modules on a static-only system by using 'make eggdrop'.
YES, when you compile statically, all the modules are linked into the main executable. HOWEVER, they are not enabled until you use loadmodule to enable them, hence you get nearly the same functionality with static modules as with dynamic modules.
It is HIGHLY recommended AGAINST using pre-compiled Eggdrops from un-trusted sources. Eggdrop has been a regular target for hacking and crashing. Distribution of pre-compiled (binary) versions of Eggdrop are the easiest way for hackers to provide you with the easiest (and most dangerous) way of gaining access to, not only your bot, but to your computer account directly. Don't advertise your pre-compiled Eggdrop binary sites on the Eggdrop list either. =P
Upgrade your Tcl, you are probably using Tcl 7.5 or earlier. Some of the commands in weed require Tcl7.6 to run, so either upgrade it or remove the offending lines from you userfile manually (those starting with '.' generally) and accept the loss of that data.
11. I get "ld-elf.so.1: Shared object "libtcl80.so.1" not found" or "eggdrop: error in loading shared libraries / libtcl8.1.so: cannot open shared object file: No such file or directory" when I try to start my bot.
'./configure' is looking in the wrong place for Tcl; it looks like it compiled with one version of Tcl and tries to load another. Maybe your sysadmin upgraded Tcl and didn't tell you. In that case, you should just need to recompile your bot.
Maybe, when upgrading, he didn't clean the old version of Tcl, and './configure' is looking for the files in the wrong places, or trying to use different versions of tcl.h and libtcl*. Smack your admin and have him install Tcl properly. ;) You can also try:
./configure --with-tcllib=<path-to-tcl-lib> --with-tclinc=<path-to-tcl-inc>
This will tell configure where to look for the Tcl files.
Try looking for libtcl by:
Try looking for tcl.h by:
If everything else fails, try to install Tcl to your home dir ;) (Suggested by dw@Undernet, email@example.com).
Possibility A: See section 11.
Possibility B: Some of the standard libraries have been compiled for static linking only on your machine, you have 3 options:
If it's your own machine, recompile Tcl using dynamic linking by using './configure --enable-shared' when you configure Tcl (not the bot) and then remake, & reinstall.
If it's not your machine, you may have to resort to 'make static' and 'make install DEST="path"' to make and install your bot.
If you are of a more aggressive sense of mind, go beat the stuffing out of your admin for having lame static libraries. :)
Copyright © 1997 Robey Pointer
Copyright © 1999 - 2008 Eggheads Development Team Eggheads Development Team