--- Ulrich Drepper <drepper@xxxxxxxxxx> wrote: > To make sure it's SELinux related, run > > /usr/sbin/setenforce 0 > > and then start syslogd again. It should work > nicely. After that run Yes syslogd starts up and runs fine. > /usr/sbin/setenforce 1 > > to turn it back on and then start syslogd again > (with the other program > still running). Since the restart should fail it > doesn't matter that > there would be two copies. But the advantage is > that now > /var/log/messages will get the appropriate message. Can't get a second on to try and come up. If I shutdown the first and try again with the setenforce 1 then it's back to the same message again. So I think this is the right track but I'm not getting any messages when I try starting the second copy.
