Description of problem: On every reboot, restorecond logs this error message to syslog: `restorecond[695]: Unable to watch (/root/.ssh/*) No such file or directory` And /root/.ssh/ doesn't exist. I don't think restorecond should throw an error in this case. I find it completely normal to not have a /root/.ssh/ folder thus restorecon should not even warn about that. When restorecond is receiving a SIGTERM (e.g. on shutdown) it throws an error too: `restorecond[709]: terminated` I don't see why this should be an error message. If you need this message at all, a INFO loglevel should be enough. Version-Release number of selected component (if applicable): policycoreutils-restorecond-2.3-18.fc22.x86_64 policycoreutils-restorecond-2.3-17.fc22.x86_64 How reproducible: on every reboot Additional info: restorecond might throw more errors, I haven't tested the whole codebase.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
Still present.
Thank you for reporting the issue. There is a pull request to decrease loglevel of the termination message. https://github.com/fedora-selinux/selinux/pull/36 As for the "watch" error, please edit your /etc/selinux/restorecond.conf (paths to be watched) accordingly.
(In reply to Vit Mojzis from comment #3) > Thank you for reporting the issue. > There is a pull request to decrease loglevel of the termination message. > https://github.com/fedora-selinux/selinux/pull/36 > > As for the "watch" error, please edit your /etc/selinux/restorecond.conf > (paths to be watched) accordingly. Thank you!
policycoreutils-2.6-5.fc27 - https://koji.fedoraproject.org/koji/taskinfo?taskID=18820403
policycoreutils-2.6-5.fc26 libselinux-2.6-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f21a1bffda
policycoreutils-2.5-20.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c89d1d37d0
policycoreutils-2.5-20.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c89d1d37d0
libselinux-2.6-5.fc26, policycoreutils-2.6-5.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-f21a1bffda
policycoreutils-2.5-20.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
libselinux-2.6-5.fc26, policycoreutils-2.6-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.