Why does SELinux often intervene when yum is updating certain things?
What I don't get is that even though SELinux claims to stop things
(never identifying yum), it seems that things get updated anyway. Is
SELinux fibbing?
I just know that someone is going to ask me what SELinux is saying.
Well, most recently, I updated everything I could and yum seems to think
it succeeded. (I've already put away that window, so I have lost yum's
victory statement.) But later I noticed the star in the task bar
indicating that SELinux has intervened. I've already put that away, but
can bring that one back up. It says <SELinux is preventing
/sbin/ldconfig (ldconfig_t) "write" to ldconfig (var_t).>.
This doesn't appear to me to have anything to do with yum, so, what is
it? It has 81 listed under Count. I'll check logwatch message (to
root) tomorrow to see what all got updated in yum. I don't know how to
check logwatch directly or how to ask yum what it did recently.
But if ldconfig got updated, and SELinux stopped it from writing
something, is the update still successful?
--
Ralph
--------------------
There are more instances of the abridgement of the freedom of the people
by gradual and silent encroachments of those in power than by violent
and sudden usurpations.
--James Madison
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
