On 16. des. 2013 13:57, jdow wrote:
> 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(/.*)?'

Right!  cache, not cahce.  Sorry about that!

I've run that command on a test system, so the rest should work.  It
would just miss labelling the proper directory with the typo.


--
kind regards,

David Sommerseth