Bug 132576 - net/openldap24-server: multipying LDAP trees on the single server is impossible
Summary: net/openldap24-server: multipying LDAP trees on the single server is impossible
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Xin LI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-12 11:50 UTC by Sergey
Modified: 2018-12-04 05:22 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey 2009-03-12 11:50:01 UTC
In OpenLDAP 2.4 (and AFAIK 2.3) there are two ways to run more than one tree on the same server:
1. To set root of the server into point. I.e. slapd.conf:

#######################################################################
# BDB database definitions
#######################################################################

database        bdb
suffix          ""
rootdn          "uid=admin,dc=mydomain,dc=net"

This way IMHO is not very well.

2. To run several daemons each with it's own config for it's own tree.

But the start script doesn't provide the possibility to run several different daemons (as apache's web server does).

I suggest to rewrite the start script in apache-style to make possible to use the second solution.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-03-12 23:45:18 UTC
Responsible Changed
From-To: freebsd-ports-bugs->delphij

Over to maintainer.
Comment 2 Carlo Strub freebsd_committer 2014-09-07 17:52:43 UTC
Is this PR still relevant?
Comment 3 Xin LI freebsd_committer 2014-09-08 09:10:57 UTC
(In reply to Carlo Strub from comment #2)
> Is this PR still relevant?

It is (and me or someone else still have to sit down and see what we can do with that).
Comment 4 w.schwarzenfeld freebsd_triage 2018-01-11 16:07:05 UTC
Same question: still relevant?
Comment 5 Kyle Evans freebsd_committer 2018-12-04 05:22:27 UTC
(In reply to w.schwarzenfeld from comment #4)

I'm interested in this, but I'm torn in approach... I see two paths forward:

1.) The www/apache24 route, which would mean we'd have slapd_profiles and profile-flavored variants of the different configuration options in rc bits, or

2.) The security/openvpn route, which would entail telling the user to link the rc script to other variants and using that as the prefix; e.g. `ln -s slapd slapd_otherdirectory && sysrc slapd_otherdirectory_enable=YES && ...`

The former would entail a lot more work than the latter, but would likely look a little cleaner. The latter would just need more minor adjustments to make sure all of the slapd_ variables use a ${name}_ prefix instead so that the link trick works.

I'm slightly leaning towards the latter method, since it would let the port user decide how they want to namespace these things rather than forcing it all under slapd_* namespace.