New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undocumented config setting use-fastdeq #692

michaelortmann opened this Issue Oct 11, 2018 · 0 comments


None yet
1 participant

michaelortmann commented Oct 11, 2018

There is a config setting named use-fastdeq (server mod).

The help for the server module displays it:

.help server module
[09:46:47] #-HQ# help server module
###  server module
   This module provides the core server support. You have to load this if you
   want your bot to come on IRC.
   The following commands are provided by the server module:
   For channel ops:
   For global masters:
      jump         dump
   Config file variables for configuring the server module:
      nick-len        server-timeout      lowercase-ctcp
      msg-rate        keep-nick           check-stoned
      serverror-quit  max-queue-msg       trigger-on-ignore
      answer-ctcp     server-cycle-wait   default-port
      check-mode-r    ctcp-mode           use-penalties
      double-server   double-mode         double-help
      use-fastdeq     stack-limit         optimize-kicks
   (Use '.help set <variable>' for more info)

But apart from that help text, there is no documentation and nothing in eggdrop.conf.

When i look into server.c, i see its automatically set to some value depending on net-type.

(I found this while analyzing how to avoid DP_MODE queue throttling for fast SASL)

Please can someone document this setting? Thank you!

Some more raw info, dont know if it helps:
use-fastdeq = 0 seems to disable all fastdeq functionality, whatever exactly that is
use-fastdeq = 2 or 3 is set for some net-types and seem to enable (mode) stacking
use-fastdeq = 1 is more than undocumented, what exactly does it? it certainly has effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment