Technical article 110589

The system clock gets reset back to present day when trying to do Year 2000 testing.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.0

Written · Last revised

Problem

I would like to do some year 2000 testing of my system. To do this, I use the date(C) (date(1)) command to set the value of the system clock forward in time to the year 2000.

I find that the time and date in the system clock keep getting reset to current time and date.

Cause

The system clock on your machine may be getting reset at boot time, or during use by an xntpd(ADMN)(xntpd(1Mtcp)) daemon, or other network time protocol daemon.

Solution

Make sure that you switch off any network time tracking daemons before performing year 2000 testing on your system, or make sure that the external time source you are referencing is feeding your server times and dates that you want to test your server on.

From the Xinuos technical article database, record 110589. Reproduced with permission. The original is at www.sco.com/ta/110589, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.