Re: Potential issue with Linux emulation?

I did NOT have NTP running (or installed for that matter) in either case.

Simply executing the following reset the date to the epoch (you need to have at least tried a make install of the redhat base package, which will reset the date too, so don't forget to adjust it before running the following):

Chroot
/usr/ports/emulators/redhat/base/w-redhat_base-8.0/fake-i386/usr/local/emul/ redhat /bin/ls

This is why I think it's a problem with the Linux emulation. Thing is, I don't know how to go about tracking the system call that is responsible for that.

//PYD -----Original Message-----
From: owner-tech@openbsd.org [mailto:owner-tech@openbsd.org] On Behalf Of Andrey Smagin
Sent: 23 August 2003 22:36
To: tech@openbsd.org
Subject: Re: Potential issue with Linux emulation?

On Sat, 23 Aug 2003 22:17:07 +0100
Andreas Kähäri <ak@freeshell.org> wrote:

> I wonder if this has anything at all to do with my problem in the

Hmm, I had similar problem just a few days ago. After upgrading two servers to -current and installing ntp package, my date gets reset to September 22, 1944 about five minutes after reboot (well, that's the time that 'date' reports, but if I reboot and check the date in BIOS, it's <something> in 1988.

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

Both servers are i386 (Gateway Server 6400 and 7200, dmesg avl. upon request), one was upgraded from source and had ntp-4.1.1 installed, another one was a clean install from snapshot and had ntp-4.1.74. Both servers were running ntp with the same settings without problems before. I uninstalled ntp from both of them and the date does not get reset now.

Also, cron really was not happy with the date changing like that - it would start using 25-35% of the CPU while doing nothing.

--
Andrey