Bowie Bailey wrote: > > There is a --no-safe-fallback option on spamc which will cause it to > exit with an error message in the case of any problems (Normally, it > always exits with a 0 exit status). If you don't want anything to go > through unscanned, you can try this setting. > >> If I have 5 spamd children available and (just to torture it) I fire >> off 50 spamc processes, what happens? > > Each spamc process will try to connect to spamd three times at 1 second > intervals. Any processes that fail to connect will let their message > through unscanned. The number of retries and the sleep interval between > them can be configured on the spamc command line. > Thanks for all the hints. I have now tried the following: I added these options to spamd --max-children=4 --timeout-child=100 and spamc --retry-sleep=20 --no-safe-fallback.
Monky I will wait and see if this improves the situation. Adding memory is of course tempting, but the server is a rented one where I cannot change the hardware but by upgrading to another (more costly) server hosting package. -- View this message in context: http://www.nabble.com/Server-overload%2C-queuing-for-SA-possible--tp22636540p22701919.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
