Comment 2 for bug 1881761

I was missing a path to scan:

  OnAccessIncludePath /home/user

With that and clamonacc running I get on access scans.

Which means that clamonacc should have it's own service file.

Though I think I'm about to give up on it, as after that I receive warnings about:

  ^lstat() failed on: /home/user/path/to/file

Though the clamav user is part of the user's group so should have access, I suspect apparmour is doing something to prevent access here. And it is not recommended to run clamav without apparmour or as root.

So I guess no one is actually using on access scanning with clamav-daemon in this way.