[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Oct files on SELinux

From: Dimitri Maziuk
Subject: Re: Oct files on SELinux
Date: Sat, 24 Nov 2012 10:30:57 -0600
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2

On 11/24/2012 3:09 AM, Julien Salort wrote:
Dimitri Maziuk <address@hidden> writes:

Disabling selinux is the first thing I do after installing a new
system. That said, audit.log should tell you which shared library is
hitting which context restriction. Then you can change selinux context
for that library.

Plugging that message into google (sans segment name probably) should
also help.

Google points to people that just deactivate SELinux.

I was puzzled that using mkoctfile directly led to a different result
than g++ -c and then mkoctfile with the .o object.
So I was under the impression that it is somehow an Octave-specific question.

As I recall that particular error comes from using shared libraries, so the first guess would be that mlockfile does "-static" whereas gcc with "ALL_CFLAGS" links dynamically. Or something -- the point is, selinux is fine as long as you don't create any files Red Hat didn't know about when they wrote up selinux policy. Otherwise

- life is too short to enable SELinux
                                Ted Tso
- It's a f*cking complex disaster, and makes performance plummet on
some things. I turn it off, and I know lots of other sane people do too.
So the !SElinux case really does need to work.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]