Thank you.
I will just go ahead and put it in ~/Library/Logs
> On Dec 17, 2019, at 05:26, Micah Snyder (micasnyd) wrote:
>
> If your clamav instance is installed to /opt/local, then your freshclam.conf
> is probably in /opt/local/etc/freshclam.conf
>
> Edit the freshclam.conf file and set t
If your clamav instance is installed to /opt/local, then your freshclam.conf is
probably in /opt/local/etc/freshclam.conf
Edit the freshclam.conf file and set the "UpdateLogFile" option to a filepath
that your user is allowed to write to.
I haven't had this particular issue on my Catalina test
Freshclam in ClamAV 0.102 will use https by default and will NOT fall back to
http. If you need to use http, you can change the DatabaseMirror option in
freshclam.conf to "http://database.clamav.net"; and that will force it to use
http. I agree that surprises aren't always funny, which is why
After updating to MacOS Catalina I get the following errors when running
freshclaim:
ERROR: Can't open /private/var/log/freshclam.log in append mode (check
permissions!).
ERROR: Problem with internal logger (UpdateLogFile =
/private/var/log/freshclam.log).
ERROR: initialize: libfreshclam init f
On Mon, 16 Dec 2019, Walker, Glen wrote:
> Hello fellow ClamAV users!
>
> I am trying to start clamonacc as a service and have created the following
> file: /etc/systemd/system/clamonacc.service:
>
> #
> [Unit]
> Description=ClamAV On Access Scanner
> Requires=clamav-daemon.socket
>
