[Date Prev][Date Next]
Re: Q: bug? slurpd only using first defined replog file?
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 22 March 2001 19:28, Mark Adamson wrote:
> You may want to look at this issue in another way. Consider that each
> database on your slapd is generating its own LDIF log, which is to be sent
> out to a list of servers.
That's what happens (or at least should) - I set the replogfile and replica
options for both ou_a and ou_b databases.
> Perhaps you should run one slurpd for each database. For 3 databases,
> have 3 slurpd.conf files, each containing only a "replogfile" directive
> and a set of "replica" lines. Start 3 slurpd processes, each with the -f
> option pointing to one of the slurpd.conf files, and the -t option
> pointing to a different tmp directory. The slapd.conf file lists all
> three replogfiles and the matching "replica" lines for each.
You mean using the include mechanism to have different slapd.conf files for
each database but also one global slapd.conf which includes the replication
core commands from files which are included by the unused (by slapd)
slapd.conf files, too? Tricky workaround but it would be nicer to either have
the manuals updated according to the current situation or better have the
software behave according to the current state of the manual. I am going to
give your proposal a try in my work.
> Consider that the slurpd has to authenticate to the slave servers,
> and you should authenticate to a DN within the database being updated. If
> you try to run one slurpd that updates 3 different databases, what DN are
> you binding as to update THREE databases?
As stated on the replica line?! Not sure whether I understand the core of
Thanks for your comment.
Heiko Nardmann (Dipl.-Ing.), firstname.lastname@example.org, Software Development
secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de),
Weidenauer Str. 223-225, D-57076 Siegen
Tel. : +49 271 48950-13, Fax : +49 271 48950-50
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----