Hi Ralf, on Debian and derived distributions (and maybe other distributions with similar mechanics in the init scripts), the `WOWorkersCount` option is overwritten by `/etc/defaults/sogo`'s `PREFORK` option. So `WOWorkersCount` is not used at all.
`PREFORK` is actually a little bit misleading here, as it is not a prefork value as for other server systems where additional processes to the ones in use are forked, but instead SOGo's `PREFORK` starts (and maintains) exactly this number of processes, no matter whether they're required (or sufficient). Regards, Jens Am 18.07.2016 um 13:34 schrieb Ralf Cirksena (c...@holmco.de): > Hi, > > I am somewhat confused re. "WOWorkersCount" / "PREFORK". > > If I set PREFORK = 3 in /etc/default/sogo with WOWorkersCount = 60 in > sogo.conf just 3 children of sogod are started. That remains on this > number even if users begin to use sogod. The only result is loooong > time waiting for synchronization. > > If I set PREFORK higher (10) then performance remains o.k. until all > workers are busy. Workers don't increase above PREFORK thus never > reaches a value near WOWorkersCount. > > Something is wrong. Clarification needed. ;-) > > > Greetings > -- Jens Erat Universität Konstanz Kommunikations-, Infomations-, Medienzentrum (KIM) Abteilung Basisdienste D-78457 Konstanz Mail: jens.e...@uni-konstanz.de
smime.p7s
Description: S/MIME Cryptographic Signature
