[Pkg-openldap-devel] Package status

[Russ Allbery]

Quanah Gibson-Mount <quanah at zimbra.com> writes:
> --On June 3, 2007 3:04:28 PM -0700 Russ Allbery <rra at debian.org> wrote:

>> I think:
>> 
>>   #375067: Running a second instance of slapd stops /etc/init.d/slapd stop
>>     from working
>> 
>> is because the PID file is overwritten, but I'm not sure the best solution
>> to the problem.

> There should never be more than one instance of slapd running from a single 
> config file.  Given that the PID file location can be specified in 
> slapd.conf, then a secondary slapd overwriting the PID file is user error 
> for failing to correctly configure their new instance (if the overwriting 
> of the PID file is indeed the problem).

Right, the problem in this case is that the init script isn't particularly
robust against a common user error, namely:

* slapd is actually still running, but the user doesn't think of that.
* User wants to debug slapd, so runs slapd -d 1.
* It fails because slapd is already running, user goes "doh."
* User runs /etc/init.d/slapd stop.
* /etc/init.d/slapd stop fails because the PID file has been overwritten.

Or at least that's what's reported in the bug.  I haven't tried it
personally.

I'm not really sure what to do about it, and I agree that it's user error,
but it would be nice if we could be more robust against that sort of
error.  Particularly given that when this happens, /etc/init.d/slapd stop
just silently succeeds without actually stopping anything.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>