+++ This bug was initially created as a clone of Bug #1414090 +++ 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): unbound-libs-1.4.20-28.el7.x86_64 How reproducible: 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 Actual results: Not in /etc/rwtab.d/unbound Expected results: File should be in /etc/rwtab.d/unbound Additional info: --- Additional comment from Tomas Hozza on 2017-01-18 09:44:03 CET --- Hello. 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.
Zbyszek, what do you think?
I think the best solution would be to get rid of /etc/rwtab.d. That whole solution is broken and I wouldn't spend any more time on making it work.
Do we have an alternative?
Yes, systemd has various facilities that implement read-only root and/or read-only system in a much cleaner way. First of all, volatile state now should be in /run, which is available since the initramfs, so the manipulations that initscripts do with /run/initramfs/state and copying files around after the transition from initramfs are unnecessary. I think nowadays it's just some dhclient-related stuff, and dhclient should be fixed to not require that, and this whole facility could be removed. And then all the other stuff should be updated to the new scheme. I haven't looked at the details, but keeping a centralized list of stuff that needs to be read-write is not the right solution.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.