ClamD and Irritating Permissions Issue: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
Experiments were done to find a better solution, but they were lost, and no time to re-create it. So every time ClamD gets upgraded, that needs to be done. You can try playing with the owners of the clamd.scan file too. Have a nice day. We didn't, until we figured out the issue. | Experiments were done to find a better solution, but they were lost, and no time to re-create it. So every time ClamD gets upgraded, that needs to be done. You can try playing with the owners of the clamd.scan file too. Have a nice day. We didn't, until we figured out the issue. | ||
Oh, and if you're searching for spamassassin, or spam or assassin or lint or --lint, because you don't remember it's ClamD causing the issue, then that's why this sentence is here. | |||
Revision as of 14:58, 27 August 2026
Every update ClamD / ClamAV? One of the files that gets updated is this one: /usr/lib/tmpfiles.d/clamd.scan.conf, which contains this: d /run/clamd.scan 0710 clamscan virusgroup
And that don't work. This does: d /run/clamd.scan 0777 clamscan virusgroup
Experiments were done to find a better solution, but they were lost, and no time to re-create it. So every time ClamD gets upgraded, that needs to be done. You can try playing with the owners of the clamd.scan file too. Have a nice day. We didn't, until we figured out the issue.
Oh, and if you're searching for spamassassin, or spam or assassin or lint or --lint, because you don't remember it's ClamD causing the issue, then that's why this sentence is here.