Alessandro Selli wrote:
> Secondly, the same document you quoted reports a very similar comment
> compared to Anselm's:
>
> «You might set |TZ| if you are using a computer over a network from a
> different time zone, and would like times reported to you in the time
> zone local to you, rather than what is local to the computer.»
>
> It also explains the rationale behind the reason one should not set
> this variable: it's just that the system's default should be adequate
> for most people.
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.
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.
Also, there's the “stockbroker's loop”:
for zone in America/New_York Europe/London Asia/Tokyo
do
TZ=$zone xclock -title ${zone##*/} -update 1
done
Anselm
--
Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- & Netz-Schulungen
[email protected], +49(0)6151-9067-103, Fax -299, www.linupfront.de
Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany
Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
