Getting lots of crashes of clamd. No indication of an issue in the clamd.log.
Installed via Homebrew.
Crash Report has:
Process: clamd [29231]
Path: /usr/local/Cellar/clamav/0.102.2/sbin/clamd
Identifier:clamd
Version: 0
Code Type:
(SOLVED)
Debugging socket connections leads to a result. The error message had nothing
to do with the communication error. Problem was caused by directory rights. So
clamonacc had the right to access the socket but not the directory where the
socket is located even when the process runs as root
No. systemd or init starts service/demons which also can be started by hand. I
meant (as written) clamonacc and clamd.
Let me explain a little bit more.I'm using CentOS 7.7 on my development systems
and on the servers. Starting both on my development station on access scanning
works well. Start
