Stephen Gran wrote:
su - clamav -s /bin/sh
strace -ff freshclam -o strace.out
I ran into this issue on one of three servers I upgraded to 0.88.2
today. After running your trace, it was obvious that another process had
the logfile already open for writing. An inspection via ps -ef | grep
f
Brian Morrison wrote:
All the time this was happening both host and dig returned the whole 15
A records for database.clamav.net quite happily, so it must be a
freshclam/resolver library issue I think.
I don't recall ever seeing this message before, but since upgrading to
0.75 this morning I have r
