ClamD and Irritating Permissions Issue: Difference between revisions
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 |
||
| (2 intermediate revisions by the same user not shown) | |||
| 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> | NEW! 2026 Solution: | ||
Create this file: <code>/etc/tmpfiles.d/clamd.scan.conf</code> | |||
Put this line in it:<code>d /run/clamd.scan 0777 clamscan mtagroup</code> | |||
Run this command: <code>systemd-tmpfiles --create --prefix=/run/clamd.scan</code> | |||
Restart clamd, mailscanner, and postfix just to get stuff flowing again. | |||
The above should correct any issues when updating with DNF and the /usr/lib/tmpfiles.d file getting overwritten. | |||
Done! | |||
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. | ||
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. | |||
Latest revision as of 17:13, 27 August 2026
NEW! 2026 Solution:
Create this file: /etc/tmpfiles.d/clamd.scan.conf
Put this line in it:d /run/clamd.scan 0777 clamscan mtagroup
Run this command: systemd-tmpfiles --create --prefix=/run/clamd.scan
Restart clamd, mailscanner, and postfix just to get stuff flowing again.
The above should correct any issues when updating with DNF and the /usr/lib/tmpfiles.d file getting overwritten.
Done!
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.