On Fri, May 23, 2014 at 09:04:29PM +0200, Karsten Bräckelmann wrote: > On Fri, 2014-05-23 at 11:30 +0200, Alex Andreotti wrote: > > is there a way to configure spamd (without patching it) to log only > > errors? > > AFAIK there is no such option. > > Though isn't that exactly what log levels are for? If you aren't > interested in the info noise, filter it out. See the journalctl > --priority option.
My fault, I'm a newbie of systemd/journalctl, should spend more time knowing it. (Even if this experience made me think that every"thing" should have a similar setting, to log errors only) > > journalctl show that idle messages are emitted about every minute > > (circa). > > Ironically, the uninteresting noise you asked to get rid of shows, there > may be some issue with your setup. (Granted, or a deliberate config > decision.) > > The --max-conn-per-child default is 200. Your ratio of child status and > spawning new children in the pasted logs is about 2:1. Did you > deliberately set that option to 2? > > The prefork child status logs are not only informational, but may also > indicate warnings or even error conditions, e.g. in case you get a > consistent high number of non-idle children. Ah! I wasn't aware about --max-conn-per-child, didn't changed it directly but recently have changed --max-children to 7 (one for earch fetchmail instance) where the comment above the setting say "make sure to not use higher than 5" ... I'm using 3 now which I guess are still a way too much for my needs, will investigate for better settings soon. Thank you very much Karsten