The "custom" timezone feature lets unRAID Server properly handle date and time adjustments for your particular time zone.

 

To use this feature, you first need to download your timezone file from our website.  Once you have identified your timezone file, right-click the link and select "Save Link As".  In the dialog box, type

timezone

for the File name.

 

Next, copy the file

timezone

to the

config

directory of your Flash.  Navigate to the 'Settings' page of the System Management Utility and select "(custom)" in the Time zone dropdown list.  Check that the Date and Time are correct and click Apply.

Tom,

 

I'm happy to report that unRAID 4.0-beta10 seems to have fixed the 3 hour "leap ahead" that took place on reboot.  In addition, the custom timezone (at least for EDT) worked like a champ.

 

Thanks,

 

BillK

G'day Tom,

I just checked this, and it seems that ACT, Australia is set to GMT-10 instead of GMT+10.

 

Are you able to confirm this for me?

 

Cheers!

Yes I'll check this.  What about the other timezones down under?  Do they seem ok?

Looks ok for a bit further down under .. NZST is looking good

Yes I'll check this.  What about the other timezones down under?  Do they seem ok?

 

The ones I've looked at (ACT, Canberra, Sydney, Darwin, Perth) All have the correct number, but are all listed as "-10", "-8" etc instead of "+10", "+8".

 

 

I don't seem to be able to get this to work.  My time zone is Eastern Standard, so I downloaded the New York file.  I followed the directions, but nothing ever changes the time displayed in the "Current date & time:" field.  The timezone designation that's in paranthesis in that field will change but not the time.  For example: right now my local time is 6:54PM, but the current time shown in unRAID is 10:54PM.  This stays the same no matter which timezone I select.  If I select GMT the time still says 10:54PM but it will be followed by (GMT).  If I select GMT +6:00 the current time will say 10:54PM (GMT -6).  If I select custom (which should be the New York file) the current time will read 10:54PM (EDT).  The EDT makes it obvious it's reading the custom file, but why doesn't the time change to 6:54PM (EDT)?

 

...

If I select custom (which should be the New York file) the current time will read 10:54PM (EDT).  The EDT makes it obvious it's reading the custom file, but why doesn't the time change to 6:54PM (EDT)?

 

When you click 'Apply' system assumes the date/time is the correct local time for the selected timezone.  After having set the timezone (or custom), just set the correct local time and click 'Apply'.

 

What will happen is that the time will be converted to UTC and stored in the motherboard real-time clock.  Next time you boot then, it will read the real-time clock and display result in your local time.  Also time stamps on files will be correct.

 

...

If I select GMT the time still says 10:54PM but it will be followed by (GMT).  If I select GMT +6:00 the current time will say 10:54PM (GMT -6). 

 

Yeah, that's an unfortunate result of a decision we made about how to display times relative to GMT.  Here's what's strange about this.  The timezone files specify the number of hours to add to local time to get UTC.  But in common use one always specifies one's local timezone as the number of hours behind (a negative number) or ahead (a positive number) UTC.  Hence for EST, we say that it's  "GMT -6", or 6 hours behind UTC.  But when timezone values are being printed out, they come straight from the file, which says that the eastern timezone has to have 6 hours added to it to get UTC and is thus displayed as GMT+6.

 

Confusing, no?  I have no idea why "they" did it this way.  We attempted to correct this by reversing the sign, but I think it just makes things more confusing 

 

That seemed to work.  I rebooted and the time "stuck".  Just curious, hat's the purpose of the timezone file if you have to manually set your local time anyhow?

Also, is the time listed for last parity check that time it started or the time it finished?