ClamD and Irritating Permissions Issue: Difference between revisions
Jump to navigation
Jump to search
Created page with "Every update ClamD? One of the files that gets updated is this one: /usr/lib/tmpfiles.d/clamd.scan.conf, which contains this: <code>d /run/clamd.scan 0710 clamscan virusgroup</code> And that don't work. This does: <code>d /run/clamd.scan 0777 clamscan virusgroup</code> 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..." |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Every update ClamD? One of the files that gets updated is this one: /usr/lib/tmpfiles.d/clamd.scan.conf, which contains this: <code>d /run/clamd.scan 0710 clamscan virusgroup</code> | Every update ClamD / ClamAV? One of the files that gets updated is this one: /usr/lib/tmpfiles.d/clamd.scan.conf, which contains this: <code>d /run/clamd.scan 0710 clamscan virusgroup</code> | ||
And that don't work. This does: <code>d /run/clamd.scan 0777 clamscan virusgroup</code> | And that don't work. This does: <code>d /run/clamd.scan 0777 clamscan virusgroup</code> | ||
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. | ||
Latest revision as of 22:58, 7 September 2025
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.