On Tuesday August 01 2006 9:26 am, Paul Howarth wrote: > If you put SELinux in permissive mode: > > # setenforce 0 > > and the problem still persists, then it's probably not an SELinux issue. > > You can re-enter enforcing mode using: > > # setenforce 1 setenforce 0 fixes the issue, which is why I figure it's Selinux -- Claude Jones Brunswick, MD, USA -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
