Thanks.
On selinux, which is the case with me, running clamd as *standalone process* is
more advantageous than running as systemd service. The reason is mentioned in
the post by someone else couple of years back. I am facing similar
issue: https://github.com/Cisco-Talos/clamav/issues/582
In case of systemd process, clamd can have graceful exit using "systemd
stop clamd@scan" but same can be achieved by "kill -TERM <pid of
clamd>" if clamd is running as standalone executable.
So given a choice, what would be reason why a user would want to run clamd@
service (instead of standalone process)?
Thanks in advance,
-Neel.
From: Matus UHLAR - fantomas via clamav-users
<clamav-users@lists.clamav.net>
Sent: Mon, 10 Jun 2024 13:06:44
To: clamav-users@lists.clamav.net
Cc: Matus UHLAR - fantomas <uh...@fantomas.sk>
Subject: Re: [clamav-users] Using clamd@ service vs launching clamd from
command line
On 10.06.24 05:57, neel roy via clamav-users wrote:
>There might be possibility that we will use more services from clamd in the
future. So we want to use clamd + clamdscan instead of clamscan.
>
>In which case I wanted to know the difference between running clamd@scan
service vs running clamd. What&#39;s the difference and what is recommended?
I'd say clamd service runs clamd.
the "service" is just systemd way to run it.
>From: &quot;Brendan Bell (brebell)&quot;
&lt;breb...@cisco.com>;
>Sent: Fri, 07 Jun 2024 22:36:02
>To: &quot;clamav-users@lists.clamav.net";
&lt;clamav-users@lists.clamav.net>;
>Cc: neel roy &lt;neelsm...@rediffmail.com>;
>Subject: Re: [clamav-users] Using clamd@ service vs launching clamd from
command line
>
>If you only want to do one scan per day, you may wish to use clamscan
instead of clamd + clamdscan.
>
>If you&#39;re doing scans on the commandline, the advantage to using
clamd is to reduce load time. &nbsp;You can load once, and then use
clamdscan to target multiple files or directories with multiple scan commands.
>
>If you&#39;re running a single scan once, even if selecting multiple
files or directories, then clamscan may be easier:
>E.g. run:
>clamscan -r DIRECTORY1 DIRECTORY2 DIRECTORY3
>&nbsp;
>From: clamav-users &lt;clamav-users-boun...@lists.clamav.net>; on
behalf of neel roy via clamav-users &lt;clamav-users@lists.clamav.net>;
>Sent: Friday, June 7, 2024 10:25 AM
>To: clamav-users@lists.clamav.net &lt;clamav-users@lists.clamav.net>;
>Cc: neel roy &lt;neelsm...@rediffmail.com>;
>Subject: [clamav-users] Using clamd@ service vs launching clamd from
command line
>&nbsp;
>Hello,
>
>https://docs.clamav.net/manual/Usage/Scanning.html#clamd reads
&quot;Once you have set up your configuration to your liking, and
understand how you will be sending commands to the daemon, running clamd itself
is simple. Simply execute the command:
>clamd&quot;
>
>But after installation I also get
&quot;/usr/lib/systemd/system/clamd@.service";.
>
>Question I have is, if I have only one conf file
&quot;/etc/clamd.d/scan.conf&quot; and all I want to do is run scan
once a day, what is the advantage of using clamd@ service vs launching
&quot;clamd&quot; from command line?
>
>And if there is no difference, which approach is recommended and why?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The early bird may get the worm, but the second mouse gets the cheese.
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat