Update sample virtual server to reflect new load Cookie behaviour

diff --git a/raddb/sites-available/ldap_sync b/raddb/sites-available/ldap_sync
index afa6bc10acc9e48899fbe21247ee257e6b5e044b..ec38b0801213104caa4902d0af45b39d80b1ba12 100644 (file)
--- a/raddb/sites-available/ldap_sync
+++ b/raddb/sites-available/ldap_sync
@@ -350,9 +350,11 @@ server ldap_sync {
        #  - If a connection experiences an error and needs to be restarted.
        #
        #  The section may return one of the following/codes attributes:
-       #  - ok/updated and &reply.LDAP-Sync.Cookie to indicate a cookie value was loaded.
-       #  - noop to indicate that no cookie was found.
-       #  - Any other code to indicate failure.
+       #  - fail / invalid / reject / disallow to indicate failure.  The section will be
+       #    retried after a delay (the ldap reconnection delay).  The sync query will not be started until
+       #    this section succeeds.
+       #  - Any other code with &reply.LDAP-Sync.Cookie populated to indicate a cookie value was loaded.
+       #  - Any other code without &reply.LDAP-Sync.Cookie populated to indicate no cookie was found.
        #
        load Cookie {
                debug_request
@@ -371,7 +373,6 @@ server ldap_sync {
 #                      &csn := %ldap("ldap:///%{LDAP-Sync.Directory-Root-DN}?contextCSN?base")
 #                      if (&csn) {
 #                              &reply.LDAP-Sync.Cookie := "rid=000,csn=%{csn}"
-#                              updated
 #                      }
 #              }
        }