On Tue, 2015-06-16 at 17:38 -0600, jd1008 wrote:
> So, I guess I have one of 2 options:
> touch /.autorelabel followed by reboot
If it's just a small number of files and/or directories, simply restore
their labels. That's much less disruptive, and this isn't windows.
man restorecon
--
tim@loca
On 06/16/2015 05:24 PM, Tahir Hafiz wrote:
On Tue, Jun 16, 2015 at 10:27 PM, Martin Cigorraga
mailto:martincigorr...@gmail.com>>wrote:
Check with SELinux Troubleshooter.
On Tue, Jun 16, 2015 at 6:24 PM jd1008 mailto:jd1...@gmail.com>> wrote:
On 06/16/2015 03:22 PM, jd1008
If you do a
sealert -a /var/log/audit/audit.log
That should output what SELinux policy was infringed.
SELinux logs to /var/log/audit/audit.log
grep AVC /var/log/audit/audit.log
is another way to parse the log file for SELinux comments.
Cheers,
Tahir
On Tue, Jun 16, 2015 at 10:27 PM, Martin Ci
Check with SELinux Troubleshooter.
On Tue, Jun 16, 2015 at 6:24 PM jd1008 wrote:
>
>
> On 06/16/2015 03:22 PM, jd1008 wrote:
> > Selinux comlained the a program "attempted write on this directory"
> >
> > but it does not say which directory.
> > I looked in /var/log but even there it does not sa
On 06/16/2015 03:22 PM, jd1008 wrote:
Selinux comlained the a program "attempted write on this directory"
but it does not say which directory.
I looked in /var/log but even there it does not say which directory.
So how can I find out which directory the program attempted the write?
The progr
Selinux comlained the a program "attempted write on this directory"
but it does not say which directory.
I looked in /var/log but even there it does not say which directory.
So how can I find out which directory the program attempted the write?
--
users mailing list
users@lists.fedoraproject.org
