[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: updatedn and refreshAndPersist in slapd.conf(5) in HEAD

--On Friday, September 14, 2007 2:17 PM +0100 Gavin Henry <ghenry@suretecsystems.com> wrote:

Dear all,

I understand that "updatedn" is not needed with refreshAndPersist?

But at http://www.openldap.org/faq/data/cache/1117.html it has it.

slapd.conf(5) in HEAD has "It is only needed in certain push-mode
replication  scenarios."

In what scenarios is it needed?

Gah, I swear I pulled that updatedn parameter out once already. slapd.conf is quite clear on what parameters go with the syncrepl directive:

yncrepl    rid=<replica    ID>	  provider=ldap[s]://<hostname>[:port]
	      [type=refreshOnly|refreshAndPersist]	[interval=dd:hh:mm:ss]
	      [retry=[<retry interval> <# of retries>]+] searchbase=<base  DN>
	      [filter=<filter  str>]  [scope=sub|one|base] [attrs=<attr list>]
	      [attrsonly]	[sizelimit=<limit>]	   [timelimit=<limit>]
	      [schemachecking=on|off]		       [starttls=yes|critical]
	      [bindmethod=simple|sasl]	   [binddn=<dn>]     [saslmech=<mech>]
	      [authcid=<identity>] [authzid=<identity>] [credentials=<passwd>]
	      [realm=<realm>]  [secprops=<properties>]	 [logbase=<base   DN>]
	      [logfilter=<filter str>] [syncdata=default|accesslog|changelog]

No where in there is updatedn.

Also in slapd.conf:

updatedn <dn>
	      This option is only applicable in a slave database updated using
	      slurpd(8).   It specifies the DN permitted to update (subject to
	      access  controls)  the  replica  (typically,  this  is  the   DN
	      slurpd(8)  binds	to  update  the  replica).  Generally, this DN
	      should not be the same as the rootdn used at the master.



Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Zimbra ::  the leader in open source messaging and collaboration