syslogd refuses to start whenever slapd process is running
Setup is as follows:
Slackware 13.0 DomU
* running Samba (acting as domain controller)
* running OpenLDAP as backend for Samba
When I first boot up the DomU the /etc/rc.d/rc.syslog script will start successfully. /dev/log exists, logging works, the whole nine yards.
Whenever the syslogd process is killed (i.e., during log rotation) the process fails to start back up. /dev/log is no where to be found and there are no log messages being written to disk.
I've discovered that stopping the slapd process (OpenLDAP server) and then trying to start the syslogd process works.
If I try to start the syslogd process whenever slapd process is running syslogd fails with "network logging disabled (syslog/udp service unknown)".
Enabling network logging doesn't fix the problem. I've also tried changing the log settings for the slapd process to no avail. I figured that stopping slapd, starting syslogd, and then starting slapd would yield some meaningful log messages about what the two are doing. I get nothing. The processes don't complain and will work happily if started in a specific order.
Has anyone else experienced this problem? It sounds like a race condition but I have no idea where to look to fix it. I could set up my log rotation with post and pre events whenever the logs are rotated but this doesn't seem right and smacks too much of being a band-aid fix.