LS,
Below is a piece of output listing, which ends with errors:
clamonacc --config-file=/etc/clamav/clamd.conf --foreground --verbose
ClamClient: client setup for continuous scanning
Clamonacc: daemon is local
ClamFanotif: kernel-level blocking feature disabled ...
ClamFanotif: max file size lim
Hi!
Many thanks Reio! That did the trick!
It needed almost about a minut to get started (I know it's a slow backup
machine), but it runs now!
It complains though about
"Failed to get properties: Unit name clamd@.service is missing the
instance name.", see below.
Nothing to worry about
On 13.10.2019 12:55, Ralf Hartings wrote:
Hi,
I had to fire-up a CENTOS 7 backup server as the main CENTOS 7 server
crashed and I updated the backup server to the latest CENTOS version
7, incl Clamav 0.101.4.
The log says, the clam service is starting, but never gets to run
properly. Every
Hi,
I had to fire-up a CENTOS 7 backup server as the main CENTOS 7 server
crashed and I updated the backup server to the latest CENTOS version 7,
incl Clamav 0.101.4.
The log says, the clam service is starting, but never gets to run
properly. Every systemctl status check I do says, it has r
