Kai Schaetzl wrote on Mon, 30 Jan 2006 21:33:05 +0100: > That is what I thought. Great, with the directive in the correct file it works now, I was able to rule out that SELinux was the culprit. Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
Cannot disable SELinux
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Cannot disable SELinux
- From: maillists at conactive.com (Kai Schaetzl)
- Date: Mon Jan 30 22:31:26 2006
- In-reply-to: <VA.0000207a.5718f2f2@xxxxxxxxxxxxxxxxxx>
- References: <VA.00002079.0a790743@xxxxxxxxxxxxxxxxxx> <1138649816.32662.42.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <VA.0000207a.5718f2f2@xxxxxxxxxxxxxxxxxx>
- References:
- Cannot disable SELinux
- From: Kai Schaetzl
- Cannot disable SELinux
- From: Sebastian Schubert
- Cannot disable SELinux
- From: Kai Schaetzl
- Cannot disable SELinux
- Prev by Date: Junk mail filtering in Evolution
- Next by Date: what pkg contains libstdc++-libc6.2-2.so.3
- Previous by thread: Cannot disable SELinux
- Next by thread: nfs export symlink
- Index(es):
 |