Am 07.08.2017 um 13:05 schrieb Carlos E. R.:
If you run clamav on an extremely low traffic mailserver there still should be the option to run it on demand e.g. from amavisd-new. Have you looked into that option?
clamd is installed in the same clamav rpm, so it can't be removed. If clamd is not running, amavis tries insistently to reach it a few times before giving up and calling clamav or clamscan directly as a separate process. This is repeated for each mail, I think. And of course, starting clamav once per mail is heavy on a fetchmail run, which can pick a thousand emails in few minutes.
I do not see how to configure amavis for not using clamd. If I start amavis, it starts clamd as a dependency.
Really? It used to be the way that you were able to comment the ClamAV-clamd entry in /etc/amavisd.conf and instead activate the clamscan in the same file. On the other hand I see a Wants=named.service clamd.service which does not allow that setup :-( I think this hard requirement of Wants=clamd.service is actually too much in any case. I tend to remove clamd.service from Wants unless someone has a smarter idea. Carlos, you can try locally as well if you like.
The best idea seems to be to configure systemd to start clamd by socket and stop it by timer. I need a howto for dummies on this. :-)
I'm not a systemd expert on it. clamav is not my package but amavisd-new is somehow. An optional socket activation actually sounds useful in any case. Please ask the maintainer or via bugzilla explicitely what he thinks about it. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org