It will also automatically offset (and gradually de-offset) if the system time jumps forward or backwards. This protects server timeouts and scheduling from improper behavior during a time jump.
For example, if the time is set back 20 minutes because it was way off when the server was started, a naive program might fail to time out any clients for 20 minutes. If a client connected at, say, 2:00, the server might schedule a timeout for 2:02 (two minutes later). If the time is then set back to 1:40, the timeout wouldn't occur for 22 minutes. Forward time jumps can create even greater chaos, potentially causing a server to time out all its clients or even crash.
ConferenceRoom's built in stable monotonic time base ensures that these kinds of problems do not occur. If the time jumps back twenty minutes, ConferenceRoom's internal timebase will continue to flow forward but at a slightly reduced rate. Over the next hour or so, the server time will synch up with the system time with no sudden or backward jumps.
ConferenceRoom will also probe remote SNTP (or NTP) servers and compute the offset (if any) between sytem time and real UTC time. It will then slew server time away from system time and towards the compute offset, keeping the server time as accurate as possible all the time.