Subject: | |
From: | |
Reply To: | |
Date: | Mon, 16 Dec 2013 04:57:07 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 2013/12/16 02:48, David Sommerseth wrote:
> On 15. des. 2013 03:13, jdow wrote:
>> On 2013/12/14 18:05, S.Tindall wrote:
>>> On Sat, 2013-12-14 at 17:36 -0800, jdow wrote:
>>>> I kinda wondered if somebody here had an idea.
>>>>
>>>> Ah well....
>>>> {o.o}
>>>
>>> I would start with:
>>>
>>> # restorecon -vr /etc/ddclient*
>>> # restorecon -vr /var/cache/ddclient
>>>
>>> and then retest in permissive mode.
>>>
>>> # setenforce 0
>>>
>>> Steve
>>>
>>
>> More or less been there done that.
>>
>> "restorecon -r /var" took a bit longer, and fixed one other unrelated
>> file. But the basic problem persisted.
>
> Most likely the EPEL package does not include a proper file context for
> the /var/cache/ddclient directory.
>
> As a quick-fix, which I believe should be fairly safe, you can add the
> dhcpc_t security context to that directory. Just run as root:
>
> # semanage fcontext -a -t dhcpc_t '/var/cahce/ddclient(/.*)?'
>
> Then you can try the restorecon command again and see if it helps.
>
>
> --
> kind regards,
>
> David Sommerseth
>
I did catch a typo:
semanage fcontext -a -t dhcpc_t '/var/cahce/ddclient(/.*)?'
should be
semanage fcontext -a -t dhcpc_t '/var/cache/ddclient(/.*)?'
{^_^}
|
|
|