Sorry aboutu the delay in replying to this (over two year old) bug. James Westby <[EMAIL PROTECTED]> writes:
> Hmmm. I can do it at will. Maybe i should have been more precise, sorry, > let's try again. Attached is my slapd.conf if that makes any difference. > I think it's because I try and start the second on a different port. >> /etc/init.d/slapd start (works) >> slapd -d 1 (fails, because port is in use) > slapd -d 1 -h ldaps://0.0.0.0:80/ (fails as db is in use) >> /etc/init.d/slapd stop (works, check pstree -u if slapd is running) > /etc/init.d/slapd stop (fails, pstree -u shows it running) >> slapd -d 1 (works, because slapd is stopped) >> /etc/init.d/slapd stop (works also, the 'slapd -d 1' is killed) > > Attached is a trace of the problem. What happened is that when you started the second slapd, it overwrote the PID file for the first slapd, at which point the init script no longer knows what PID slapd has and will try to stop the debugging version. I don't think this is a problem that can really be fixed. You have to go to some effort to overwrite the PID file, as you found out, and the init script really relies on the PID file being correct. My inclination is to close this bug as something we can't really fix, although let me know if you object. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
