I can't get Eggdrop to start automatically on boot.

[aarons]

Hi,

I've tried starting eggdrop automatically in boot and it wont work. I've got ircd running and thats fine. now, in the /etc/rc.d/init.d directory i have a executable shell script called eggdrop that should start the bot automatically. i put links to it in all of hte rc#.d dir's cuz i dont know exactly which one to put it in. it doesn't work tho. in boot, nothing is mentioned about eggdrop and nothing in thesyslog. when i run the script from the command line it says it cannot find language modules... then i tried putting "cd to/that/dir" in there and it works at the console then. but in boot it still doesn't (this i figure because it can't cd due to limited shell). i did a strings on the eggdrop executable file and found it appears to be looking for the language files in ./language. i tried modifying the path variable before the eggdrop starts and it still does not work. if anyone has a sample or example shell script that woudl help me here, id be very grateful.
oh, its redhat 7.1

biga

[ppslim]

Do not use this method to start eggdrop.

It will try and start it as root (not certain, havn't ever gotten round to doing any sort of tests), which eggdrop will refuse to run as.

Setup a crontab entry, using the botchk script.

Refer to the documentation that comes with eggdrop for this.

While it will not start as soon as the system is up, it can and will start within a very small and limited time.

[aarons]

thanks for your help. being a moron, i completely missed that part of the documentation. After a while i got it to work. in my version, though, the botchk file asked for the configuration file, in which i filled in eggdrop.conf like i thought it should be. in autobotchk, it looked like it was tryign to run that file, which obviously would not work, so i switched that to ./eggdrop and now it works perfectly.

[ppslim]

In reality, running the config file would work.

IE, my config is called idibot.conf

typeing "./idibot.conf" at the shell, will load my eggdrop.

This works, by making sure the first line of your config file, points to the egdrop file (IE, the ./eggdrop you where talking about), plus, making sure the file has the exacute bit set.

[soulm4t3]

I have problems starting the bot using crontab. The email i received is

/bin/sh: /home/users/soulm4t3/eggdrop1.6.6/eggdrop/scripts/botchk:
No such file or directory

I tried running ./soulm4t3.conf and the error message appear again.

I have the following in the topline of soulm4t3.conf

#! /home/users/allie/eggdrop1.6.6/eggdrop

What could be the problem?

I can run the bot by typing ./eggdrop soulm4t3.conf

Any suggestions/comments/help?

[heichers]

I am having a similar problem....

I can start the bot just fine if I am in the bots directory (./thrillbot.conf, bot's directory is /home/tnchat/eggdrop), but if I do a crontab for it, or if I try starting it (from say the account's home directory eg "/home/tnchat" and use the command "eggdrop/thrillbot.conf"), it crashes with the following...

[12:32] LANG: No lang files found for section core.
[12:32] --- Loading eggdrop v1.6.10 (Fri Apr 18 2003)
[12:32] Listening at telnet port 3334 (all)
[12:32] MSG20B dns: /usr/home/tnchat/modules/dns.so: cannot open shared object
file: No such file or directory
[12:32] MSG20B channels: /usr/home/tnchat/modules/channels.so: cannot open
shared object file: No such file or directory
[12:32] Tcl error in file '/home/tnchat/eggdrop/thrillbot':
[12:32] invalid command name "channel"
while executing
"channel add #coasterchat {
chanmode "+nt-lik"
idle-kick 0
stopnethack-mode 0
flood-chan 10:60
flood-deop 3:10
flood-kick 3:10
flood-join..."
(file "/home/tnchat/eggdrop/thrillbot" line 178)
[12:32] * MSG534

Top line of the conf file is "/home/tnchat/eggdrop/eggdrop"

OS is Redhat 8.

Funny is we migrated to Redhat 8 from FreeBSD (clean install, and I recompiled the bot for the new OS), and FreeBSD we didn't have this problem. It's almost like it's trying to start in whatever directory I am currently in.

[ppslim]

Did you re-create the botchk file too.

Note how it is tryign to load the DNS and other modules from the /usr/ directory.

This is likely teh cause of a incomplete migration on your part.

[heichers]

I recreated the botchk... we were thorough in our migration and had a checklist of what needs to be taken care of.

Also, /home is an alias of /usr/home, and works either way (of course don't ask me on this one, I did not rebuild our server, and the owner of the ISP we partner with "likes it this way" in his Linux setups.

Also, from what I've been told, there have been no problems in RH 7.3, but when it comes to RH 8.0, there seems to be a problem. I've duplicated the problem on my local test box (and that is definately a fresh server install, no migration or anything).

[ppslim]

I have no issues with RH8. There are no special patches applied to the system, and it worked from day 1, up and including now, where up3date patches have been applied.