Browse Source

Note that MX_MIN_WORKER_DELAY should be set to zero.

master
Dianne Skoll 3 months ago
parent
commit
b8bf5d0c5d
Signed by: dianne GPG Key ID: 685A5A5E511D30E2
  1. 1
      etc/default/mailmunge.example.in
  2. 14
      pod/mailmunge-multiplexor.pod.in

1
etc/default/mailmunge.example.in

@ -54,6 +54,7 @@
### Delay between starting each worker even on a very busy system
### -W option to mailmunge-multiplexor; defaults to 0 in C code
### Note that we *do not* recommend setting this option to a non-zero value.
# MX_MIN_WORKER_DELAY=
### Allow connections to queue if all workers are busy?

14
pod/mailmunge-multiplexor.pod.in

@ -102,12 +102,14 @@ I<waitTime> seconds. The default value for I<waitTime> is 1.
If you use this option, C<mailmunge-multiplexor> will I<never>
activate a worker until I<waitTime> seconds have elapsed since the
last worker activation. This could result in mail being tempfailed
if worker activations do not keep pace with incoming mail. However,
it may be preferable to tempfail mail rather than allow the load
on your server to spike up too quickly. The default value for this
option is 0, meaning that C<mailmunge-multiplexor> will start
workers as quickly as necessary to keep up with incoming mail.
last worker activation. This could result in mail being tempfailed if
worker activations do not keep pace with incoming mail. However, it
may be preferable to tempfail mail rather than allow the load on your
server to spike up too quickly. The default value for this option is
0, meaning that C<mailmunge-multiplexor> will start workers as quickly
as necessary to keep up with incoming mail. Except in very unusual
situations, you should need to use this option and we do not recommend
that it be used.
=item -z I<spooldir>

Loading…
Cancel
Save