Bon bah finalement j’ai reussi en faisant une petite pirouette. J’ai appris qu’on pouvait utiliser l’ancien système de configuration.
il suffit de supprimer ou renommer le slapd.d :
Slapd prendra maintenant en compte le fichier slapd.conf =)
Je vous met le miens au passage, comme ca si un jours quelqu’un cherche a faire une replication miroir sous squeeze il y arrivera rapidement :
sur le premier ldap :
et copier :
[code]# This is the main slapd configuration file. See slapd.conf(5) for more
info on the configuration options.
#######################################################################
Global Directives:
ServerID 1
Features to permit
#allow bind_v2
Schema and objectClass definitions
include /etc/ldap/schema/core.schema
include /etc/ldap/schema/cosine.schema
include /etc/ldap/schema/nis.schema
include /etc/ldap/schema/inetorgperson.schema
include /etc/ldap/schema/samba.schema
Where the pid file is put. The init.d script
will not stop the server if you change this.
pidfile /var/run/slapd/slapd.pid
List of arguments that were passed to the server
argsfile /var/run/slapd/slapd.args
Read slapd.conf(5) for possible values
loglevel none
Where the dynamically loaded modules are stored
modulepath /usr/lib/ldap
moduleload back_hdb.so
moduleload syncprov.la
The maximum number of entries that is returned for a search operation
sizelimit 500
The tool-threads parameter sets the actual amount of cpu’s that is used
for indexing.
tool-threads 1
#######################################################################
Specific Backend Directives for @BACKEND@:
Backend specific directives apply to this backend until another
‘backend’ directive occurs
backend hdb
#######################################################################
Specific Backend Directives for ‘other’:
Backend specific directives apply to this backend until another
‘backend’ directive occurs
#backend
#######################################################################
Specific Directives for database #1, of type @BACKEND@:
Database specific directives apply to this databasse until another
‘database’ directive occurs
database hdb
The base of your directory in database #1
suffix “dc=domain,dc=local”
rootdn directive for specifying a superuser on the database. This is needed
for syncrepl.
rootdn "cn=admin,dc=domain,dc=local"
rootpw toto
Where the database file are physically stored for database #1
directory “/var/lib/ldap”
The dbconfig settings are used to generate a DB_CONFIG file the first
time slapd starts. They do NOT override existing an existing DB_CONFIG
file. You should therefore change these settings in DB_CONFIG directly
or remove DB_CONFIG and restart slapd for changes to take effect.
For the Debian package we use 2MB as default but be sure to update this
value if you have plenty of RAM
dbconfig set_cachesize 0 2097152 0
Sven Hartge reported that he had to set this value incredibly high
information.
Number of objects that can be locked at the same time.
dbconfig set_lk_max_objects 1500
Number of locks (both requested and granted)
dbconfig set_lk_max_locks 1500
Number of lockers
dbconfig set_lk_max_lockers 1500
Indexing options for database #1
index objectClass eq
index entryCSN,entryUUID eq
#provider configuration
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
#consumer configuration
syncrepl rid=001
provider=ldap://192.168.3.111
type=refreshAndPersist
retry="60 +"
searchbase="dc=domain,dc=local"
scope=sub
schemachecking=on
bindmethod=simple
binddn="cn=admin,dc=domain,dc=local"
credentials=toto
mirrormode on
Save the time that the entry gets modified, for database #1
lastmod on
Checkpoint the BerkeleyDB database periodically in case of system
failure and to speed slapd shutdown.
checkpoint 512 30
The userPassword by default can be changed
by the entry owning it if they are authenticated.
Others should not be able to see it, except the
admin entry below
These access lines apply to database #1 only
access to attrs=userPassword,shadowLastChange
by dn=“cn=admin,dc=domain,dc=local” write
by anonymous auth
by self write
by * none
Ensure read access to the base for things like
supportedSASLMechanisms. Without this you may
have problems with SASL not knowing what
mechanisms are available and the like.
Note that this is covered by the ‘access to *’
ACL below too but if you change that as people
are wont to do you’ll still need this if you
want SASL (and possible other things) to work
happily.
access to dn.base="" by * read
The admin dn has full write access, everyone else
can read everything.
access to *
by dn=“cn=admin,dc=domain,dc=local” write
by * read
For Netscape Roaming support, each user gets a roaming
profile for which they have write access to
#access to dn=".*,ou=Roaming,o=morsnet"
by dn="@ADMIN@" write
by dnattr=owner write
#######################################################################
Specific Directives for database #2, of type ‘other’ (can be @BACKEND@ too):
Database specific directives apply to this databasse until another
‘database’ directive occurs
#database
The base of your directory for database #2
#suffix “dc=debian,dc=org”[/code]
pensez a modifier le fichier pour qu’il corresponde a votre domaine et a votre mot de passe admin.
Pour le fichier slapd.conf du deuxieme ldap cest exactement la meme chose sauf qu’il faut mettre ServerID 2 et l’adresse du provider (cest a dire l’adresse du ldap01). Je les ai marqué en rouge pour mieux identifier les changement a faire.
(figure_1)
