Kevin Horton
Guru
- Joined
- Dec 2, 2015
- Messages
- 730
I'm running FreeNAS-9.10-STABLE, updated from 9.3-STABLE yesterday, using the update tool in the GUI.
I noted that the time zone had gone to the first in the list after the system rebooted following the update (Africa/Abidjan). I live in Ottawa, Canada, so I set it to America/Toronto, and confirmed the time was correct, both in the GUI and in the CLI using the date command.
Today, I noted that some scripts (set up in Tasks -> Cron Jobs) that email me status info at particular times had arrived four hours early (i.e, they arrived at the UTC time, not the local time). With 9.3, these cron tasks would trigger at the expected local time.
Is this an expected change?
Hardware (I doubt it is relevant, but rules are rules):
Motherboard: SuperMicro X10SL7-F
CPU: Intel G3258
RAM: 16G Crucial CT2KIT102472BD160B/CT2CP102472BD160B
PSU: SeaSonic SSR-550RM
Boot USB flash drives:
San Disk Cruzer Fit Usb Flash Drive 16 GB
Kingston 16GB DT Microduo 3C
Hard drives: 5 x Western Digital Red 4 TB in RAIDZ2
I noted that the time zone had gone to the first in the list after the system rebooted following the update (Africa/Abidjan). I live in Ottawa, Canada, so I set it to America/Toronto, and confirmed the time was correct, both in the GUI and in the CLI using the date command.
Today, I noted that some scripts (set up in Tasks -> Cron Jobs) that email me status info at particular times had arrived four hours early (i.e, they arrived at the UTC time, not the local time). With 9.3, these cron tasks would trigger at the expected local time.
Is this an expected change?
Hardware (I doubt it is relevant, but rules are rules):
Motherboard: SuperMicro X10SL7-F
CPU: Intel G3258
RAM: 16G Crucial CT2KIT102472BD160B/CT2CP102472BD160B
PSU: SeaSonic SSR-550RM
Boot USB flash drives:
San Disk Cruzer Fit Usb Flash Drive 16 GB
Kingston 16GB DT Microduo 3C
Hard drives: 5 x Western Digital Red 4 TB in RAIDZ2