World: r3wp

the main reason I am running this image is so that I have an imap 
server to use with rebelBB !

damm... gone back 12 hours after rebooting.

how about tzconfig

and now it has been set correctly using hwclock --hctosys

don't have a tzconfig program

Oh, it just makes sure  /etc/localtime is copied from proper /usr/share/zoneinfo 
and puts the tz in /etc/timezone...my directories are for Debian

Ok.  Well, Gnome shows me the correct timezone.

Does that help?

do a cat /etc/timezone

nothing

Then make sure that /etc/localtime is identical to the /usr/share/zoneinfo/Canada/Eastern 
where the Canada/Eastern part is for me...

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144894

Other images keep the correct time?  I had to add --directisa  to 
get the system time to hardware in the hwclock executed at shutdown. 
 That was just to get the PC to hold UTC.

one is out by an hour only ( day light saving I guess ).

What does hwclock --show say

Ubuntu says 6:46 EDT April 6, but i have not round to setting this 
up yet.

Gee, all my images have different times!

How about ntpdate.  Does it correct itself?

Fun stuff isn't it.  :)

hwclock --show says 10:23 NZST

it's lost 20 mins since I set the time!

ntpdate says socket is being used

Debian comes with ntpdate-debian that uses ntpdate 0.debian.pool.ntp.org 
 (for the (first) server arg)

How does one set the time from bash ?

date

I used tzselect to reset the timezone, but the time is still wrong.

After the tzselect was there an ntpdate or hwclock --hctosys executed?

no

hwclock --hctosys is not setting the time correctly now

Off by how many hours?

hwclock --utc  (if hardware is utc) or hwclock --localtime  can effect 
things.

20 mins

I used date to set the time correctly .. now going to wait 20 mins 
and see what happens

Write a little script like   forever [print now/exact wait 00:05:00] 
 and log it or just monitor

/exact = /precise sorry.

already lost 2 mins :(

Battery failing...?  Something not right in the system clock ticker?

Or is it just the fedora image?

must be a vmware bug

because the actual hardware clock is correct.

and it's just fedora core 6 image that is doing this.

Something might be eating interrupts...you know to ...help

well, the only thing I have running is uniserve, and the imap server

cheyenne

perhaps I should run a script that fixes the date every minute!

Heehee...if you can't beat 'em

now where is the ntp protocol ?

A google of   fedora time drift vmware  shows a lot of info

Debian I just executed  apt-get install ntp  and then forgot about 
it.

crontab ntpdate !