On 2017-08-07 12:42, Carlos E. R. wrote:
On 2017-08-07 08:33, Per Jessen wrote:
Instead of the daemon, I could call it from amavis, one process per mail. But this impacts scan speed. Could the daemon be started "on demand", and be killed a minute after the last email goes through?
Perhaps, but you're looking to save 500Mb on a machine with 8Gb?
I notice those 500, believe me. The machine responds a bit better just after I killed clamd.
I see two avenues. The first one is to modify my "get mail" script to first start clamd service, and then manually stop clamd service after mail has been processed (I do not yet easily see how to stop it automatically). But clamd gets also called when a mail goes out (unneeded, but it does so). The other method, much cleaner, would be to start service when the socket gets something, which I believe systemd can do but I have never done; no idea where to start. Guide for dummies? Then stop it after a minute of no use, also automatically. Is this possible? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)