Description of problem:
The unbound-anchor.timer updates the file /var/lib/systemd/timers/stamp-unbound-anchor.timer, so shouldn't that be noted in /etc/rwtab.d/unbound, for example?
Version-Release number of selected component (if applicable):
Enable unbound and notice that /var/lib/systemd/timers/stamp-unbound-anchor.timer is touched every 24 hours.
Steps to Reproduce:
1. yum install unbound unbound-libs
2. systemctl start unbound.service
3. notice that /var/lib/systemd/timers/stamp-unbound-anchor.timer is touched every 24 hours
Not in /etc/rwtab.d/unbound
File should be in /etc/rwtab.d/unbound
As far as I can tell, the file must be created by systemd as a side effect of running timer units. I noticed, that the /var/lib/systemd/timers/ directory contains also files for other timer units. I think the directory itself should be in rwtab and the configuration should be rather shipped by systemd.
Note that the file is not created by Unbound directly.
Agreed. Thanks for fixing the component.
After consulting this with lnykryn, we decided it would be best addressed in initscripts: https://github.com/fedora-sysv/initscripts/pull/65
We just need to backport: https://github.com/fedora-sysv/initscripts/commit/73f52775e7c92c7428759d6d41b2d39bcce541ab
# grep /var/lib/systemd/timers /etc/rwtab
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.