Andrey Ivanov wrote:
Hi, I have noticed that the attribute nsDS5ReplicaUpdateSchedule works in a strange way (maybe it's how it is supposed to work). When i put it to nsDS5ReplicaUpdateSchedule: 0000-2359 0123456 the replication at midnight (00:00) seems to be blocked. The message that i observe in the logs every midnight is [28/Oct/2008:00:00:00 +0100] NSMMReplicationPlugin - agmt="cn="Replication from ldap-1.polytechnique.fr to ldap-2.example.com"" (ldap-2:636): Incremental protocol: event update_window_opened should not occur in state wait_for_changes [29/Oct/2008:00:00:00 +0100] NSMMReplicationPlugin - agmt="cn="Replication from ldap-1.polytechnique.fr to ldap-2.example.com"" (ldap-2:636): Incremental protocol: event update_window_opened should not occur in state wait_for_changes If i suppress the schedule (the attrribute nsDS5ReplicaUpdateSchedule) completely, everything is fine. So, it seems that the server excludes the first value in the time range (xxxx-yyyy ddddddd) from the authorized interval. Is it a bug or it is supposed to work that way?
That's the way it is supposed to work.
Andrey Ivanov tel +33-(0)1-69-33-99-24 fax +33-(0)1-69-33-99-55 Direction des Systemes d'Information Ecole Polytechnique 91128 Palaiseau CEDEX France -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
