Description of problem: When using readonly root with selinux disabled, the fedora-readonly service always reports as failed. Version-Release number of selected component (if applicable): initscripts-9.34-2.fc16 How reproducible: Always Steps to Reproduce: 1. Configure a system with readonly-root (/etc/sysconfig/readonly-root) 2. Boot with selinux=0 3. systemctl --failed Actual results: fedora-readonly.service has failed Expected results: fedora-readonly.service is not listed Additional info: The issue is the helper script /lib/systemd/fedora-readonly exists with the wrong exit status. [ -n "$SELINUX_STATE" ] && [ -e "$path" ] && restorecon -R "$path" is not quite the same as if [ -n "$SELINUX_STATE" ] && [ -e "$path" ]; then restorecon -R "$path" fi The difference being the status. If the fedora-readonly.service fails would that effect prevent other services which Require fedora-readonly from running?
Fixed in http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=1c38e273b3b2114ae9525f1ad28ad4f44ce6bf55, thanks!
initscripts-9.35-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/initscripts-9.35-1.fc17
Package initscripts-9.35-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.35-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3459/initscripts-9.35-1.fc17 then log in and leave karma (feedback).
initscripts-9.34.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.34.1-1.fc16
initscripts-9.34.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.34.2-1.fc16
initscripts-9.34.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.