|Re: [chrony-users] tempcomp.log not created (on Fedora 17 & 20) when chronyd started from systemd|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Wed, Mar 05, 2014 at 02:10:18PM +0100, Ferry de Jong wrote:
> Unfortunately I'm unfamiliar with fixing these SELinux policy issues. Can
> it been seen as a shortcoming in the default SELinux policies that chronyd
> can not read files in sysfs, or should one add a definition rule oneself?
> Any suggestion how I should do it for this specific case?
I've filed a bug in our bugzilla, we'll see if this can be allowed in
the default selinux policy. In the meantime you can allow it in a
local policy module.
> Wouldn't it be nice if chronyd reports some sort of logging if it can not
> access the tempcomp specified file, now it seems to silently ignore the
> inability to open/read the file, making the diagnosis of this issue harder
> than necessary.
Yes, that would help. I'll add some error messages to the code.
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.