> On Apr 26, 2019, at 1:50 PM, Gregory Farnum <[email protected]> wrote: > > Hmm yeah, it's probably not using UTC. (Despite it being good > practice, it's actually not an easy default to adhere to.) cephx > requires synchronized clocks and probably the same timezone (though I > can't swear to that.)
Apps don’t “see” timezones, timezones are a rendering transform of an absolute time. The instant “now” is the same throughout space and time, regardless of how that instant is quantified. UNIX wall time is just one such quantification. Problems ensue when the rendered time is incorrect for the time zone shown in the rendering. If a machine that is “not using time zones” shows that the time is 3PM UTC and one lives in London, the internal time will be correct. On the other hand, if they live in NYC, the internal time is incorrect. This is to say 15:00UTC rendered at 3PM in NYC is very wrong *because it’s not 3PM in London*, where UTC is true. tl;dr: Make sure that your clock is set for the correct time in the time zone in whatever rendering is set. It doesn’t matter where the system actually resides or whether the TZ matches it’s geographic location.
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
