S2 TimeZoneOffset Question

[bmckim]

I need a little help. When I run tzoffset.tcl on my S2 unit, the tzoffset.txt file produces a rediculously large number of seconds for the offset, as you can see...

# <tzoffset>-64796400</tzoffset>
set info(tzoffset) -64796400

So, using TiVoWeb Plus, I navigated to this location in the TiVo db...

http://192.168.1.3/mfs/State/LocationConfig

and found this...

LocationConfig 4316/10 {
Version = 5
PostalCode = 40205
TimeZoneOffset = -18000
IndexPath = /State/LocationConfig
}

I am suspect that the TimeZoneOffset should equal -5 because I am in the Eastern Time Zone, instead of -18000.

Sooooo.....

Could an S2 user check this out on your unit and reply.

And if I am correct, I am hoping someone might be able to tell me a procedure for correcting this in the db, or what might be causing it.

And help would be appreciated.

bmckim@usa.com

[stevel]

The offset is in seconds: -18000 seconds is -5 hours.

[bmckim]

Yes, but the -64796400 is basically 3600 times too large. That value should be -18000, and I am trying to figure out why. Did you check the TimeZoneOffset value on your S2 using TiVoWeb and find it to also be -18000? If so, I wonder what might be causing tzoffset.tcl to generate a value which is 3600 times too big.

(The fact that there are 3600 seconds in an hour would suggest that someplace that should be counting in hours is actually holding a value that is in seconds.)

[Jamie]

Yes, but the -64796400 is basically 3600 times too large. That value should be -18000, and I am trying to figure out why. Did you check the TimeZoneOffset value on your S2 using TiVoWeb and find it to also be -18000? If so, I wonder what might be causing tzoffset.tcl to generate a value which is 3600 times too big.

(The fact that there are 3600 seconds in an hour would suggest that someplace that should be counting in hours is actually holding a value that is in seconds.)The units for the timezone offset value in MFS changed for versions >= 4.0. It's now in seconds; it was hours in the older versions. This is not a error in the DB; it's a bug in the tcl script. The script needs to be adjusted to take into account the tivo software version.

A search for tzoffset.tcl will yield a lot of history on this issue, mainly WRT the version in mfs_ftp. I believe the issue was addressed in TivoWebPlus v1.1.