[mythtv-users] Timezones and Dual Booting

[Brian May]

>>>>> "Harry" == Harry Orenstein <ho_9 at hotmail.com> writes:

    Harry> My problem is that I have my hardware clock set up
    Harry> for local time and when I load listings using the
    Harry> grabber I get all of the data off my 4 hours (since it is
    Harry> now DST).  I have forced a --tz-offset -0400 into the
    Harry> command line used for tv_grab_na_dd to offset this,
    Harry> but it seems kind of kludgy.

    Harry> Perhaps there is something in CSV that addresses
    Harry> this and I am unaware of it?  Perhaps I should be
    Harry> setting my hardware clock to UTC to overcome this?
    Harry> All comments and suggestions are welcome.

MythTV (AFAIK) doesn't read the hardware clock, it reads the system
clock.

The system clock should be the same regardless of how the time is
stored in the hardware clock.

If it isn't working correctly, then either you have your time zone set
incorrectly, or haven't told the boot scripts that your clock is
stored in UTC, or the hardware clock isn't set to local time.

On my Debian system I use the following three commands to find all
three times:

snoopy:~# hwclock --show
Tue Apr  6 14:51:14 2004  -0.266389 seconds
snoopy:~# date
Tue Apr  6 14:51:33 EST 2004
snoopy:~# date --utc
Tue Apr  6 04:51:36 UTC 2004

The first one shows your hardware clock, the next one shows the system
clock, translated to local time. The third one is the value of the
system clock in UTC.
-- 
Brian May <bam at snoopy.apana.org.au>