Hi Sachin,
Before looking into the policy differences between the two systems... Is there any reason you're not patching the RHEL6.6 system?
If if all works under RHEL6.8 then patching the RHEL6.6 system could get your daemon working.
Cheers
Phil
Sachin Gaikwad ---14/02/2017 15:17:46---Hi all, I am running a daemon process (C++ program) on RHEL 6.6 with SELinux
From: Sachin Gaikwad <sachin.kernel@xxxxxxxxx>
To: selinux@xxxxxxxxxxxxxxxxxxxxxxx
Date: 14/02/2017 15:17
Subject: SELinux enabled + rsync + Permission denied (13)
Hi all,
I am running a daemon process (C++ program) on RHEL 6.6 with SELinux enabled. This process eventually executes "rsync" to do file-copy operation. It is failing with following error:
---------------------------------8<--------------------------------------------
rsync: change_dir "/home/foobar/source/" failed: Permission denied (13)
rsync: ERROR: cannot stat destination "/mnt/other_volume/testData": Permission denied (13).
---------------------------------8<--------------------------------------------
Question: Why is rsync failing with this error? I checked permissions of "source" and "target" and both have permissions for the user.
Other testing data:
1) I tested this with "SELinux" disabled and rsync succeeds.
2) I tested this with "SELinux" enabled and launching process from terminal. In this case "rsync" works fine. So, it looks like it is something to do with "SELinux permissions" to process which do not have tty?
3) On other system RHEL 6.8, SELinux enabled, process as daemon: rsync works fine. I compared SELinux configuration of both these systems, but couldn't find anything to reason it out. If you need, I can attach SELinux configurations.
Thanks in advance,
Sachin_______________________________________________
selinux mailing list -- selinux@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to selinux-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ selinux mailing list -- selinux@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to selinux-leave@xxxxxxxxxxxxxxxxxxxxxxx
