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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881761 Title: clamav-daemon on access scanning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1881761/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
