On 06/07/2019 06.19, stakanov wrote:
In data sabato 22 giugno 2019 00:14:15 CEST, Carlos E. R. ha scritto:
Carlos, I have been bothered by the same problem and resolved by putting a timeout of 200 for spamd in my system. As this is AFAIU a thing about how to do it best, I share my thing which is doing editing amavis via nano. As the system is running systemd: first of all I went root with
$ su -
then I entered
# systemctl edit --full spamd.service
which opens nano in order to edit
/etc/systemd/system/
in the section [service] you join the value: TimeoutStartSec=200
I am sure you can experiment to lower that value, but with 200 I am fine and did not experience problems. You save with Ctrl + X and are asked whether you want to save the value via a spamd.service.nnnn file were nnnn stands for any systemgiven number. This creates in /etc/systemd/system reliably the file spamd.service file that contains the desired timeout value for spamd daemonized verson. It should survive any normal system upgrade AFAIK and that way one does not mess up systemd settings.
Probably that was trivial for you, but as I did follow superficially the thread, at the end I did not understand if you solved.
Yes, I solved it, earlier than this thread. Initially I edited the main configuration file, and then here I found out that we could do it for this service only, so that a an override file would do. And then Mathias Homann told us about the edit command in systemd: systemctl edit spamd.service Using "--full" I don't think is appropriate, because if there is an update to the service you will miss it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)