I have sucessfully created, started and loaded my first bot, but now would like to add another. I have another process that is available for me to use.
Do i need to create another bot directory? The first one is myBot.
How would i create and configure another bot directory? Do i need to telnet to the shell and create new directory from there?
also, is there a section or some documentation on adding second bot to the shell? Im still reading so much and have not found that section yet, and if i did, i missed it and may not have understood.
i created another conf file and ftp'd it up to the same dir as the first bot. Then i putty'd up to the shell and did the ./eggdrop -m myBot2.conf and appeared to load sucessfully.
I went into the channels added in the conf file and the bot did not come in.
was there something i was supposed to configure thru putty that i missed?
I generally wouldn't recommend running multiple eggdrops from the same directory, always seems to lead to conflicts with crontab and netbots, among other reasons... is there a specific reason you wanna run multiple bots from the same directory, such as to save disk space, or are you simply curious...? This is also covered under F.A.Q. #24
toad wrote:i created another conf file and ftp'd it up to the same dir as the first bot. Then i putty'd up to the shell and did the ./eggdrop -m myBot2.conf and appeared to load sucessfully.
I went into the channels added in the conf file and the bot did not come in.
was there something i was supposed to configure thru putty that i missed?
I run on average 4 bots from the one folder on each shell account I have (33 bots all up), their respective confs are identical except for the host, ip, nick used, log names and user/chan filenames; they all have the same "home" channel and they all load the same modules required to connect to IRC.
I'd suggest you look at your second conf to see what modules it's not loading compared to the first (successfull) conf.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM