29 Apr
2016
29 Apr
'16
12:41 a.m.
Howard Chu hyc@symas.com schrieb am 28.04.2016 um 19:54 in Nachricht
Time values are based on the time(3) subroutine, which can also be affected by anyone explicitly resetting the system clock. Of course, such an event would
also be visible on regular syslog timestamps etc.
Is ldapd's uptime using time() minus some fixed value? Why not using the POSIX CLOCK_MONOTONIC value instead.
Actually you gave a clue: the slapd is running in a VM, and the VM had been live-migrated. Maybe the glitch originated from there.
Regards, Ulrich
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/