On Tue, May 25, 2010 at 04:33:53PM -0700, Jerry Franz wrote: > Are you running with SELinux on? Now there's a good question, it turns out. I'd assumed CentOS followed the pattern of most distros in having it not be in strictest mode out-of-the-box, but in /etc/selinux/config: SELINUX=enforcing I can see where to turn it off in /etc/selinux/config. But what's the step to get it to restart, other than rebooting the system? Reload a module? And I'd point out that _nothing_ about smbd was being logged previously, until upgrading samba from the CentOS 5.4 version to the current version started throwing this error: May 25 19:22:26 xyz smbd[5455]: [2010/05/25 19:22:26, 0] lib/messages.c:message_init(132) May 25 19:22:26 xyz smbd[5455]: ERROR: Failed to initialise messages database Isn't selinux supposed to be competent enough to log events that it presents? There's nothing from it in anything under /var/log. So if selinux is causing this whole problem, it's pretty incompetent at it. Anything worth blocking is certainly worth logging, right? Whit