On Fri, Mar 6, 2009 at 12:11 PM, Craig White <craigwhite@xxxxxxxxxxx> wrote: > did you 'relabel' the entire filesystem? - that's pretty much necessary > if you've been running the system without having SELinux running, at > least in permissive mode. SELinux had been running in permissive. I did not disable during install because of the warning about having to relabel the entire filesystem if I wish to re-enable it subsequently. That seems like a bad idea so I've always ran it in permissive rather than enforcing due to the first experience. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: SELinux resource hog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: SELinux resource hog
- From: Noob Centos Admin <centos.admin@xxxxxxxxx>
- Date: Fri, 6 Mar 2009 12:27:14 +0800
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <1236312684.8080.2.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <667c2e1e0903052000yf292a00nfad3cdeabb6e472e@xxxxxxxxxxxxxx> <1236312684.8080.2.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References:
- SELinux resource hog
- From: Noob Centos Admin
- Re: SELinux resource hog
- From: Craig White
- SELinux resource hog
- Prev by Date: Re: SELinux resource hog
- Next by Date: Re: compile driver before X starts
- Previous by thread: Re: SELinux resource hog
- Next by thread: Re: SELinux resource hog
- Index(es):
 |