On Wed, 22 Feb 2006, Steve Thomas wrote: > > i googled a bit and found this related to fedora3 and SELinux: > > http://forums.mysql.com/read.php?11,20759,21482#msg-21482 > > I had seen that page, but didn't know what selinux was (thought it was a > distro!) so I thought it was irrelevant. After checking it out, it turns > out that that's what the problem is/was! I disabled selinux and the first > test after rebooting seems to have worked. > > I don't believe I need selinux for anything, as our environment's pretty > well controlled and we've made do without it for.. well forever, but I'll > probably have to learn about it eventually so I suppose I'll start looking > into it... > > Thanks a million Matthias. I'm kind of embarrassed that I was looking at > the answer yesterday and dismissed it... :\
your welcome :) > For Glen and the archives: > I disabled selinux by setting the SELINUX environment variable to > "disabled" in /etc/selinux/config and rebooting. when installing fedora, it ask for SELinux behavior (enabled / warnings only / disabled), IIRC right after "firewall default settings". since i wasnt sure of what it really "protects" or is used for, i always set it to "warnings only". still too lazy, reading the manpages :) regards, Matthias
