Detailed information for the notes.ini Keyword: 

Server_disable_TimeSync


Short Description: Disabled the polling intervall which stay in sync with the OS time.

Description:
Problem
After upgrading a Lotus® Domino® server to release 8, you notice the Domino server's time may run faster or slower than the operating system time. Why does this occur?
Cause

Domino experienced time creep. Time creep can be a slowly increasing difference between Domino and Operating System time from a few seconds to minutes even hours over days. Or time creep can be a time jump where there is a sudden jump in Domino time versus OS time, where the most common jump was 1hr:13 mins as shown in this console log sample:

[00673:00002--1241363936] 12/16/2008 10:21:22 AM  RnRMgr: Error processing calendar profile document (NoteID: NT000008FA) in database mail/userone.nsf: Cannot find user in Domino Directory
[00643:00002--1241003488] 12/16/2008 10:21:22 AM  SchedMgr: Error processing calendar profile document (NoteID: NT000008FA) in database mail/userone.nsf: Cannot find user in Domino Directory
[00673:00002--1241363936] 12/16/2008 11:34:40 AM  RnRMgr: Error processing calendar profile document (NoteID: NT000008FA) in database mail/usertwo.nsf: Cannot find user in Domino Directory
[00635:00002--1241236960] 12/16/2008 11:34:40.56 AM AddInMain> DEBUG_TIMECREEP: (1): before AddInLogMsg.

You can see that the time jumps from 10:21:22 AM to 11:34:40:56. This causes email to be delivered with an incorrect time stamp and it causes reporting applications that use Domino time to be incorrect.

Time creep is mostly caused by inconsistent OS ticks versus OS time: Windows API - GetTickCount() and Solaris API - gethrtime() proved to return discrepant ticks in some cases.
The time jump is caused by bugs in the Domino time package.

These were not mainly observed in previous versions of Domino, since, due to some function calls, Domino indirectly synchronized more often to the OS time, whereas in 8x that stopped, primarily for performance reasons.

Resolving the problem

    These issues have been reported to Quality Engineering as SPR# DBRH7FRQ6R and WBKK7EKQ7X, and have been fixed in Domino 8.0.2 FP1, 8.0.3, and 8.5.

    SPR# DBRH7FRQ6R deals with an issue where ticks outside of the semaphore lock which allows Domino to stay in sync with OS time via polling. The default polling interval is 5 minutes, but you can change it using one of these notes.ini parameters:

    SERVER_TIMESYNC_INTERVAL = 1 - every 5min (default)
    SERVER_TIMESYNC_INTERVAL = 2 - every 1min
    SERVER_TIMESYNC_INTERVAL = 3 - every 60min
    SERVER_DISABLE_TIMESYNC=1 - disable polling

    SPR# WBKK7EKQ7X fixes an old relic of keeping track of the Previous Ticks introduced in Domino 4.0 for OS2, and assures that accurate ticks are obtained.





Default value:
None

Syntax:
Server_disable_TimeSync=0 / 1

Example:
Server_disable_TimeSync=1

UI equivalent:
There is no kown UI setting for this notes.ini variable. But you can specify this setting in the notes.ini settings tab of the configuration settings document.


Applies to:
Server


Valid for version:
8.0.2