4 ms·

I lived through the changes of 2005 as a sysadmin: * https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time https://en.wikipedi

I lived through the changes of 2005 as a sysadmin: * https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chan... From a Unix perspective (Solaris, Linux, IRIX), it was fine. And Ontario has provisionally passed getting rid DST changes (sadly in favour of going to year-round DST), and IMHO it will be fine again if it is ever finalized: * https://toronto.ctvnews.ca/ontario-passes-legislation-to-make-daylight-time-permanent-1.5205131 https://toronto.ctvnews.ca/ontario-passes-legislation-to-mak...

inferiorhuman 4y ago
Sure. And we all survived Y2K. Point being that setting your servers to UTC is one less thing to worry about. I'd flip the argument on its head and posit that there's no compelling reason to use anything other than UTC. So long as you keep your TZ database up-to-date local time is likely to be not-so-problematic. Once you have that one server in a closet that didn't get updated, all bets are off.
- throw0101b 4y ago
  > Point being that setting your servers to UTC is one less thing to worry about. It's only one less thing to worry about if you worry about it in the first place. I do not. > I'd flip the argument on its head and posit that there's no compelling reason to use anything other than UTC. There is a compelling, or at least useful, reason for me; from another reply I did: Using UTC when all of my servers are in one timezones actually decreases clarity, as I live in America/Toronto with my daily existence, and which is what my laptop and (mechanical) wristwatch are set to. If I less(1) the logs I now have to do mental math as to "when" things happen because the hour number it says in the logs does not match my human reality. If I look at something now (at Mar 25 21:09) the logs would say "Mar 26 01:09" which is not "now" in my mind.

inferiorhuman 4y ago

Sure. And we all survived Y2K. Point being that setting your servers to UTC is one less thing to worry about. I'd flip the argument on its head and posit that there's no compelling reason to use anything other than UTC. So long as you keep your TZ database up-to-date local time is likely to be not-so-problematic. Once you have that one server in a closet that didn't get updated, all bets are off.

throw0101b 4y ago
> Point being that setting your servers to UTC is one less thing to worry about. It's only one less thing to worry about if you worry about it in the first place. I do not. > I'd flip the argument on its head and posit that there's no compelling reason to use anything other than UTC. There is a compelling, or at least useful, reason for me; from another reply I did: Using UTC when all of my servers are in one timezones actually decreases clarity, as I live in America/Toronto with my daily existence, and which is what my laptop and (mechanical) wristwatch are set to. If I less(1) the logs I now have to do mental math as to "when" things happen because the hour number it says in the logs does not match my human reality. If I look at something now (at Mar 25 21:09) the logs would say "Mar 26 01:09" which is not "now" in my mind.