On Wed, 2 Oct 2013, Chase, John wrote:
Part of the problem is that SELinux is not writing any
messages anywhere we can see
In a Red Hat derived environment, when enabled SELinux uses
one of two possible file locations when in enforcing, or
permissive modes:
/var/log/messages
-or-
/var/log/audit/audit.log
depending on whether the 'auditd' is running
With the unit in permissive mode, start in two consoles, a:
tail -f ...
on each file and it should have message appear if that is the
issue
but if a person is randomly adding improper versions and
'feeling their way around' debugging an issue, there is no
telling whan they may have damaged. See:
http://orcorc.blogspot.com/2013/06/phone-call-ive-got-this-sick-machine.html
about only debugging machines from a known state
-- Russ herrold
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
