Hi, On Sun, 09.03.2008 at 16:31:27 +0000, Stuart Henderson <[EMAIL PROTECTED]> wrote: > You have several recommended options: > > - dump your database, uninstall, install the unFLAVORed version > and restore your database.
I tried that, but now run into the problem that now, slapd can't be stopped. Maybe it has something to do that the server in question runs as a syncrepl client together with TLS (master is openldap-server-2.3.33p1-bdb on 4.2). In any case, the only way to get slapd down seems to be to kill -9 it, which is _very_ugly_ for other reasons. My other slapd instances don't have such a problem. At the end of the log, it says ------------------ daemon: shutdown requested and initiated. slapd shutdown: waiting for 2 threads to terminate ------------------ which points to a handful of tickets in the OpenLDAP tracker. It would be very nice if you could suggest something with less impact than backporting 2.3.43 from -current. In any case, I'd like to know whether you'd prefer such problems to be reported on misc@, ports@ (I didn't do that to keep clutter out while approaching freeze), or upstream's tracker directly. TIA! Kind regards, --Toni++
