[Date Prev][Date Next]
> IMPORTANT UPDATE:
> Is it normal for a 'slapd' server to correct itself via a restart of
> the slapd process? Currently, I have one Consumer that is 2-records
> behind in Synchronization - I restarted his process and the records
> immediately were replicated. This normally is NOT standard behavior.
> Can anyone explain? Is this expected? Indicative of another problem?
That's what the "refresh" in "refreshAndPersist" is about. Any freshly started
consumer will automatically sync up to the current state of the provider.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/