On Sun, Jul 17, 2011 at 12:27 AM, Jan de Groot <j...@jgc.homeip.net> wrote: > On Sat, 2011-07-16 at 05:40 -0400, Eric Bélanger wrote: >> On Sat, Jul 16, 2011 at 4:09 AM, Jan de Groot <j...@jgc.homeip.net> wrote: >> > On Fri, 2011-07-15 at 20:48 -0400, Eric Bélanger wrote: >> >> Sure. I just did it in my WIP PKGBUILD to not forget. >> >> >> >> As no-one seems to know about the db moving part, I'm leaning into >> >> keeping --localstatedir=/var/lib/openldap. I'll wait for a day or two >> >> in case someone wants to pipe in, unless you want me to go forward to >> >> get the new openladp package done for the tcp_wrappers removal. >> > >> > What db-moving part exactly? Doesn't the current package install the >> > database in /var/lib/openldap, and isn't that the logical place for it? >> > >> > >> >> The current package use the --localstatedir=/var/lib/openldap >> configure option. That does 2 things: >> - it creates a /var/lib/openldap/openldap-data/ directory where the db is >> stored >> - it creates a /var/lib/openldap/run/ directory where the unix ldapi >> socket will be located >> >> Although this is a reasonnable location for the db, you said in a >> comment on FS#21051 that /var/lib/openldap/run/ is a weird location >> and that /var/run would be better. If we want to change the location >> of the ldapi socket to /var/run, we'll need to use >> --localstatedir=/var as configure option. However, this will also >> change the expected location of the db to /var/openldap-data/ hence >> the db moving business. >> >> I guess it all boils down wether the weirdness of having the socket >> /var/lib/openldap/run/ is important enough to worth the hassle of the >> db moving. > > What about patching? > > http://patch-tracker.debian.org/patch/series/view/openldap/2.4.25-1.1/wrong-database-location > > We're not the only one facing this problem. > >
Coincidentally, I ran into the Debian patches tonight and was about to mention it here. We could patch to keep the db in the current location and have the socket in /run. Patching would be trivial and low-maintenance. That's probably the best solution unless someone objects. Debian also have a patch to have an errors log file in /var/log instead of /var, I'll apply it regardless. Eric