I see that slapd does not actually write the 'replica: 192.168.247.130:389' line to the ldif entries it puts in the 'reglogfile'. So that looks like the source for one issue. On Friday 12 January 2007 14:46, Quanah Gibson-Mount wrote: > --On Friday, January 12, 2007 2:34 PM -0600 "Jeremy M. Guthrie" > > <jeremy.guthrie@berbee.com> wrote: > > So more information about my problem: > > if I change: > > replica uri=ldaps://192.168.247.130:389/ > > to > > replica uri=ldap://192.168.247.130:389/ > > THEN I get a slightly different replication log created by Slurpd. > > However, when I examine that file, it is missing: > > replica: 192.168.247.130:389 > > How do you intend to do LDAPS over port 389? I assume what you want is > startTLS on port 389. Or else, turn on LDAPS on port 636.... > > --Quanah > > -- > Quanah Gibson-Mount > Principal Software Developer > ITS/Shared Application Services > Stanford University > GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html -- -------------------------------------------------- Jeremy M. Guthrie jeremy.guthrie@berbee.com Senior Network Engineer Phone: 608-298-1061 Berbee - A CDW Company Fax: 608-288-3007 5520 Research Park Drive NOC: 608-298-1102 Madison, WI 53711
Attachment:
pgpPcdZhyoT5K.pgp
Description: PGP signature