Hi Fabiano and list, Please forgive me, I just realized that I wasn't, indeed, running from master. I'll try again with the proper version and come back if needed.
Thanks! Victor El 10/10/16 a las 10:09, Fabiano Fidêncio escribió: > Victor, > > On Mon, Oct 10, 2016 at 10:04 AM, Victor Tapia > <[email protected]> wrote: >> 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? > > Are you running git master? This issue is supposed to be already > solved by > https://github.com/SSSD/sssd/commit/b8ceaeb80cffb00c26390913ea959b77f7e848b9 > > Best Regards, > _______________________________________________ sssd-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
