It was found during testing for a user-identified issue that post changes made to Timezone that cron.d will not apply the new timestamp until after reboot. This means that until you reboot the Orange Pi CPU that cron.d assumes you are still on New York time.
Expected performance
Cron.d should be on the selected time without the need for a reboot of the device
Workaround
Rebooting the CPU after updating timezone corrects the issue.
It was found during testing for a user-identified issue that post changes made to Timezone that cron.d will not apply the new timestamp until after reboot. This means that until you reboot the Orange Pi CPU that cron.d assumes you are still on New York time.
Expected performance Cron.d should be on the selected time without the need for a reboot of the device
Workaround Rebooting the CPU after updating timezone corrects the issue.