Hi list, I've faced a race condition when SSSD boots in a machine with a big clock drift. This is what I see:
1. SSSD starts before the network is up, queries the LDAP server without success and sets a retry timer (~60 secs) 2. NTP starts and corrects the clock, 1 hour back for example. 3. SSSD takes ~60 secs + the drift correction (1 hour) to retry the connection. In this particular scenario the credentials cache is disabled, so the wait time to login is noticeable. How feasible would it be to use a monotonic clock for this kind of timed events? Kind regards, Victor _______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
