It means, if you have duplicate processes running of the same executable file and .conf file kill them and make sure only one process of ./eggdrop is running. It's like you have two seperate internet explorer windows open, so you can browse from two different windows.
·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee) PS: Guys, I don't accept script helps or requests personally anymore.
==================================
The same effect will occur if crontab is set for the bot and it's screwing up. Has happened to me off and on, 3 to 4 bots connecting because crontab screwed. If you do actually have a crontab set for the bot, remove it.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
I have the same problem with 3 proceses of eggdrop running for 1 bot.
I tryed the ./configure --disable-tcl-threads option, but when I do that, the bot doesnt connect to irc. It will connect fine with the normal ./configure and 3 processes but I cant have that many processes for one bot. I also cant telnet to the bot when doing disable-tcl-threads. Why is this?
I even removed the 3 source scripts/blah.tcl lines at the end of the conf and it still uses 3 processes for the bot.
If you read above, you will see that i tried using --disable-threads, but when I do that, the bot doesnt connect to irc, and i cant connect to it to see whats wrong. Its like it just isnt there. It wont work unless i do configure normally which gives me 3 processes.
Do you get 1bot to join, but see 3 processes on the shell?
If so is the shell running debian?
I had a shell that ran on debian and that started 2 baby processes, nothing you could do about it as far as i could tell. So i got rid of the shell and only run bots on bsd instead
havokator wrote:If you read above, you will see that i tried using --disable-threads, but when I do that, the bot doesnt connect to irc, and i cant connect to it to see whats wrong. Its like it just isnt there. It wont work unless i do configure normally which gives me 3 processes.
nah, you tried this on eggdrop's configure
I meant Tcl's configure; you do know that Tcl libraries are built separately from eggdrop, don't you?
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use