-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2012 08:05 AM, mark wrote:
> On 11/21/12 05:17, Daniel J Walsh wrote:
>> On 11/20/2012 03:56 PM, m.r...@5-cent.us wrote:
>>> I upgraded a development server last week, and it started spewing
>>> selinux errors to the log. I googled. What final
tried to install a new centos6.3 and apache. No luck to reproduce what
you've been through. Don't know what the error is you had but I dont get
any error from my log files.
Banyan He
Blog: http://www.rootong.com
Email: ban...@rootong.com
On 2012-11-21 9:08 PM, mark wrote:
> On 11/2
On 11/21/12 00:55, Banyan He wrote:
> On 2012-11-21 4:56 AM, m.r...@5-cent.us wrote:
>> I upgraded a development server last week, and it started spewing selinux
>> errors to the log. I googled. What finally *seems* to have stopped it was
>> a) setsebool -P httpd_setrlimit 1
>> b) yum downgrade se
On 11/21/12 05:17, Daniel J Walsh wrote:
> On 11/20/2012 03:56 PM, m.r...@5-cent.us wrote:
>> I upgraded a development server last week, and it started spewing selinux
>> errors to the log. I googled. What finally *seems* to have stopped it was
>> a) setsebool -P httpd_setrlimit 1 b) yum downgrade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2012 03:56 PM, m.r...@5-cent.us wrote:
> I upgraded a development server last week, and it started spewing selinux
> errors to the log. I googled. What finally *seems* to have stopped it was
> a) setsebool -P httpd_setrlimit 1 b) yum downgra
what's the error? How do you produce it?
Banyan He
Blog: http://www.rootong.com
Email: ban...@rootong.com
On 2012-11-21 4:56 AM, m.r...@5-cent.us wrote:
> I upgraded a development server last week, and it started spewing selinux
> errors to the log. I googled. What finally *seems* to
On 20/11/12 20:56, m.r...@5-cent.us wrote:
> I upgraded a development server last week, and it started spewing selinux
> errors to the log. I googled. What finally *seems* to have stopped it was
> a) setsebool -P httpd_setrlimit 1
> b) yum downgrade selinux-policy\*
>
> This is on a 6.3 box. Has an
I upgraded a development server last week, and it started spewing selinux
errors to the log. I googled. What finally *seems* to have stopped it was
a) setsebool -P httpd_setrlimit 1
b) yum downgrade selinux-policy\*
This is on a 6.3 box. Has anyone else seen this behaviour?
mark
__
8 matches
Mail list logo