On 13 June 2013 14:20, Vishesh kumar wrote:
> You can also use audit2allow, audit2allow will write allow rule for you.
>
>
Not a good option in this case considering there's reasonable likelihood of
messed up labelling...
While the tool audit2allow will create a module that will allow the
activi
You can also use audit2allow, audit2allow will write allow rule for you.
Thanks
On Thu, Jun 13, 2013 at 5:47 PM, James Hogarth wrote:
> >
> > Can someone confirm or deny that making the Logical Volume inactive and
> > then repeating the chcon should change the link to the correct context?
>
> F
>
> Can someone confirm or deny that making the Logical Volume inactive and
> then repeating the chcon should change the link to the correct context?
First off don't use chcon.
What's the output of restorecon -Fvv /path-to-file ?
It seems very odd in the first place for anything in /dev to have
Hi
A few days ago we rebooted a server and found that one of the Logical
Volumes would not mount at boot, but mounted cleanly manually.
So I traced the problem to SE Linux. Specifically the context for
/dev/mapper/VolGroup01-lv_
staff is wrong.
s -lsahZ /dev/mapper/VolGroup01-*
lrwxrwxrwx. root
4 matches
Mail list logo
