Editing the botchk file to automatically restart your bot

Wissensdatenbank

Eggdrop daemonizes. Screen/tmux are for irssi/weechat, not the bot. Persist with crontab via autobotchk. Prefer that over hand-editing botchk.

autobotchk (do this)

From the bot directory, after the conf works:

cd ~/botdir
./scripts/autobotchk botnick.conf

Useful flags:

./scripts/autobotchk botnick.conf -noemail

That writes a crontab entry that runs botchk every few minutes. Confirm:

crontab -l

You should see a line pointing at scripts/botchk (or the generated wrapper) in your bot dir.

scripts/botchk needs four paths: bot dir, binary, conf, userfile. They must match reality. Then crontab:

0,10,20,30,40,50 * * * * /home/YOU/botdir/scripts/botchk >/dev/null 2>&1

crontab -e to insert. pwd from the bot dir for the path.

Do not "keep it in screen so it stays up." That is how you lose the bot on a detached session and violate the point of a daemon.

AUP still applies: max 2 IRC connections per shell to a given network.