[rubenv]

That's true if you need to clean up temporary files every night or make a backup.

But what if your cronjob has an effect in the physical world, locally? E.g. open the parking gates every morning.

The world is inherently messy :-)

[roryirvine]

That sort of thing would be best handled by your own user's crontab, so would naturally inherit that user's TZ.

If you must run it as root, you can specify a CRON_TZ variable on a per-file basis, which will override the default.

[cesarb]

> That's true if you need to clean up temporary files every night or make a backup.

Making a backup is usually reserved for the quietest hours of the morning, so that it does not compete as much for resources with the normal operation of the system; in my experience, the quietest hour is usually around 4:00 local time.

[tankenmate]

Well assuming that the gates don't move timezones. But obviously jobs that need to run for a given timezone should be configured to run in that timezone.

[cube00]

Unless the gates need to open at 2:30am and in the case of daylight savings time that hour is skipped.