Eggheads: Removing queue delays completely.

[CoolCold]

Hello Derek,

Saturday, December 31, 2005, 10:12:45 AM, you wrote:

DK> Hello CoolCold,

DK> Friday, December 30, 2005, 12:16:37 PM, you wrote:

>> Take a look at http://eggdrop.org.ru/scripts/putserv_vs_putfast.tcl
>> I've wrote this script to eliminate any flood limits eggdrop has in
>> it's queues except that are used by modules in C, but i guess this is
>> possible too.
>> Load this script before all others ( while this is not strictly
>> required ). It overrides default putserv/puthelp/putquick commands
>> with our own and send data to server without any checks. I hope this
>> is what you need.

DK> Woow, I'm in credits (in a very first procedure, what an honor =)))

:))

DK> Anyway, I would like to warn you about putdccraw, it doesn't use any
DK> queue so it's probably what Richard wants, but when I was using it (to
DK> send sharing commands from a tcl script) it didn't behaved well, some
DK> commands didn't go to the bot as they should.
DK> I'm guessing that eggdrop was probably sending his own commands and
DK> putdccraw was cutting between that and sending it's own stuff.

DK> Put that's just my assumption, after I noticed problems I decided not
DK> to use it... Perhaps with server communications there might be no
DK> problems at all...

DK> As for settings maybe this could help a little bit:
DK> You could set net-type to 5, and then:
DK> set use-penalties 0

DK> Some network use penalties, for flood connection, after specific limit
DK> is reached they don't perform any command, but still collecting
DK> commands sent by bot. When the buffer gets full server disconnect the
DK> client. To avoid this, eggdrop also calculates penalties, and waits
DK> when the limit is reached.

DK> After this setting bot will turn that off, but the queues will still
DK> work (so this script still probably will be faster).

DK> I don't belive there is a variable that turns off queues at all, and
DK> most likely to accomplish this you would need to modify server module.

If your are using hybrid 7.x, you may give your bot irc operator
rights and add to auth section in config:

can_flood = yes;
exceed_limit = yes;

smth like this:
auth {
        user = "*eggdrop@*";
        #spoof = "coolcold.org";
        have_ident = no;
        class = "opers";
        spoof_notice = no;
        #password = "blablabla";
        exceed_limit = yes;
        kline_exempt = yes;
        gline_exempt = yes;
        can_flood = yes;
};


and in general section:
        /* no oper flood: increase flood limits for opers. */
        no_oper_flood = yes;

        /* true no oper flood: completely eliminate flood limits for opers
         * and for clients with can_flood = yes in their auth {} blocks
         */
        true_no_oper_flood = yes;

This will remove any flood limits for your bot. Just creating auth
section, but not giving eggdrop irc operator status, will remove time
limit, but keep buffer limits.

Anyway you should refer to your ircd manual.


np: 101-the_thrillseekers_present_nightmusic_volume_1-disc_1_the_dj-tsp

Best regards,
CoolCold [COOLCOLD-RIPN]