RESOLVED with help of https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-Managing_Services_with_systemd-Unit_Files#brid-Managing_Services_with_systemd-Extending_Unit_Config

I simply had to (removed former approach first):

1) cp /usr/lib/systemd/clam@.service /etc/systemd/system/
2) made my changes in copied file
3) perfomed systemctl daemon-reload
4) Checked changes with systemd-delta:
[.. snippet ..]
[OVERRIDDEN] /etc/systemd/system/clamd@.service → /usr/lib/systemd/system/clamd@.service--- /usr/lib/systemd/system/clamd@.service 2019-08-23 17:07:29.000000000 +0200+++ /etc/systemd/system/clamd@.service 2019-08-26 14:17:31.144758369 +0200@@ -1,5 +1,5 @@ [Unit]-Description = clamd scanner (%i) daemon+Description = Customized clamd scanner (%i) daemon Documentation=man:clamd(8) man:clamd.conf(5) https://www.clamav.net/documents/ # Check for database existence # ConditionPathExistsGlob=@DBDIR@/main.{c[vl]d,inc}@@ -9,4 +9,5 @@ [Service] Type = forking ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf-Restart = on-failure+#Restart = on-failure+TimeoutSec = 600

Thanks to everyone who helped. Great community indeed!

On 26.08.2019 11:27, Fajar A. Nugraha via clamav-users wrote:

On Mon, Aug 26, 2019 at 4:18 PM Herbert via clamav-users <clamav-users@lists.clamav.net> wrote:

Hi all,

System Fedora 5.2.9-200.fc30.x86_64
ClamAv 0.101.4

I wonder why a DNF update changes my customized
/usr/lib/systemd/clam@,service file.

... because you shouldn't have modified that file?

https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administering-systemd/#modifying-existing-systemd-services

Background:
I had to add/change the following configurations in above mentioned file
to overcome
a timeout issue.

TimeOutSec = 600
#Restart = on-failure # to avoid restarting on timeout failure

If it's an addition, you could probably use systemd drop-in configuration file instead, e.g.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-Managing_Services_with_systemd-Unit_Files#brid-Managing_Services_with_systemd-Extending_Unit_Config

IMHO an update should not change the service files, but instead install
a new version of this file(s)
with an appropriate extension. In addition DNF update should inform
about this with a warning.

Are you sure you're not confusing /usr/lib/systemd with files under /etc ? AFAIK what you wrote is correct for files in /etc.

--

Fajar
_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml