hi, i'm running 50 eggdrops on 1 shell. all of which are connecting 2 1 channel on my network. they are detecting their join as a flood nomatter which flags i set 2 eachother. is there anyway 2 disable it?
another problem is. they are on +i mode channel and they set +im when they detect a flood. now, when they remove the lock protection they remove the -im mode (even though +i was there b4 the "flood") can they remember which modes they added and set only those modes off?
In order to look into this any further, I require ALL of the following:
1) a copy of your sentinel.tcl or netset.tcl showing your sentinel settings
2) an unbutchered channel log from your client (e.g. mIRC) with showing the incident, including 5 minutes of activity before and after
3) an unbutchered bot log from the time of the incident which displays sentinel's log messages and all the usual stuff, including 5 minutes of activity before and after
If you have these, please send them to my e-mail address, the first part is 'slennox' and the second part it '@egghelp.org'.
well, the real problem is the fact you're running 50 bots on one shell, with the same ident - wtf is the point? I do seriously hope its your own irc server, else I can see some serious klines coming your way.
Hm, what's the point of running 50 bots on 1 shell?
They are pretty useless that way, beside you want to use them as floodbots.
If the shell lose connection or is down all 50 bots are gone.
But may be there#s a good reason and i don't know it yet. Would be nice to learn something new
well... it is my server. i'm the admin of IrCQ-Net (the ICQ irc services). i have many channels 2 secure and i'm not gonna use 1 bot 2 do it. i prefer giving each bot 5-8 channels 2 deal with. this way they won't ever ping out.
slennox, i'll give u the logs 2morrow when i'm at work. ty all 4 replying...
From the logs you provided, I suspect the ChanServ madly joining/parting the channel as the cause of the join-part flood detection being triggered.
Incidentally, having 50 bots all running sentinel.tcl with the same settings, all setting +i/m and noticing the channel after the lock, creates one hell of a mess. There's nothing you can do about the +i/m flood (except running the script on fewer bots), but you should enable cfnotice/bfnotice on two or three bots only.
In your post you mention that the channel is +i by default. sentinel.tcl does cause problems for +i or +m channels. I'll look into adding an enforced modes (as set with .chanset) check to make sure any modes present there are not removed by the script.