Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 1
    personally, I would switch the the timezone that is most suitable to your requirements - of course, a user ... nevermind comment below mentioned what I was going to say Commented Apr 5, 2023 at 6:53
  • 9
    Sounds like "personal preference" to me. Do it whatever way makes sense to you. Also you can use multiple timezones / per process, by setting TZ (or CRON_TZ). Though that may be even more confusing than a single timezone for everything... Commented Apr 5, 2023 at 6:53
  • 2
    +1 to CRON_TZ. Our servers are contractually mandated to be UTC, but they "live" in the US east coast. Thus, it's set to America/New_York, as is TZ in .bash_profile. Commented Apr 5, 2023 at 8:03
  • 2
    I would: (1) set up one of your servers as time server that is queried by the others (time and timezone changes will only have to applied once); (2) read the logs via a perl wrapper that corrects timezone issues (adds or subtract hours); (3) store current time difference to UTC in a file on every server. All servers should live in a homogenous UTC environment; CET is for being easier read by humans. Commented Apr 5, 2023 at 15:53
  • 3
    what do you mean "still"? Is there some reason to assume there would have been more reason for that before, but not now?? Commented Apr 5, 2023 at 17:00