On Wed, Apr 1, 2015 at 10:34 AM, Anselm Lingnau <[email protected]> wrote: > IOW, as the system administrator, don't set the timezone for users by > defining TZ in /etc/profile; use /etc/localtime instead. Individual > users are still free to set TZ to something that works for them.
System-wide, has _always_ been /etc/localtime. Some distros have used additional files to track information. As I used an example, attitude of many newer *ctl utilities has always been use _only_ Upstream paths, config files, etc... by _default_, and one must _justify_ any additional paths, config files, etc... that aren't in the kernel, LibC or other core library, LSB-FHS, etc... > I usually sell this to my class participants as an advantage. With other > operating systems, you set the clock according to the system timezone > and that is it. On Linux, determining the actual (civic) time is just a > matter of formatting the second count from 1 Jan 1970 0:00 UTC into > something that is appropriate for that particular user, and this makes > things like the remote-login case straightforward to handle for > individual users; the operating system kernel's job is just counting the > seconds accurately. Just remember ... UTC only works for "here and now." I.e., past or future dates should be localtime, _unless_ they were recorded "here and now" at that time, and off-set. There are many articles on this in the industry, from simple daytimers to trading systems. I got deep into Olson DB over a decade ago due to the latter. -- bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
