yes
On 7/11/2021 2:08 PM, Gary Bowling wrote:
Another point, I guess if we leave the cron in place.
It looks to me like we can just disable the clamav-freshclam.service.
Is that correct?
Thanks, Gary
On 7/11/2021 4:03 PM, Gary Bowling wrote:
Thanks, Gary
On 7/11/2021 4:01 PM,
Another point, I guess if we leave the cron in place.
It looks to me like we can just disable the
clamav-freshclam.service.
Is that correct?
Thanks, Gary
On 7/11/2021 4:03 PM, Gary Bowling
Thanks, Gary
On 7/11/2021 4:01 PM, Eric Broch wrote:
If
the service is running, updates are happening, but if the clamav
developers are doing away with freshclam daemon, which seems
likely, option 2 seems to be the way to go.
If the service is running, updates are happening, but if the clamav
developers are doing away with freshclam daemon, which seems likely,
option 2 seems to be the way to go.
On 7/11/2021 1:55 PM, Gary Bowling wrote:
Thanks Eric.
So I kinda of like having the service show up in toaststat as
Thanks Eric.
So I kinda of like having the service show up in toaststat as
it's an easy way to check things. Which would encourage me to take
option 1.
However, is the "new" way of doing it, to do it in cron? If it
is,
Freshclam doesn't start because databases are now updated by cron job
'/etc/cron.d/clamav-update' in 'freshclam.service' file. If cron job
file exists freshclam daemon is not necessary.
Pick one of two options:
1)
vi /usr/lib/systemd/system/clamav-freshclam.service
replace
I see where Chandran had this same issue a few weeks ago. What
did you do to resolve it?
Thanks, Gary
On 7/11/2021 1:03 PM, Gary Bowling
wrote:
Running a toaster on CentOS 7, with everything updated every
Running a toaster on CentOS 7, with everything updated every
couple of months. Just did an update on my server. The update took
me from
clamav-update-0.103.2-1.el7.x86_64 >
clamav-update-0.103.2-2.el7.x86_64
All the other clamav packages are also
