From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Anthony Sorace In-Reply-To: Date: Mon, 12 Nov 2012 21:29:08 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <5625B926-DCE8-49B9-B37D-74943FA82458@9srv.net> References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Attempts to set timezone don't stick? Topicbox-Message-UUID: d56b70c8-ead7-11e9-9d60-3106f5b1d025 On Nov 12, 2012, at 21:15 , Phineas Pett wrote: > Ah, thanks. The manual has answered a lot of my questions so far, but > apparently I need to read more carefully; but still, if I am logged > into a remote system in a different time zone, shouldn't my client be > able to display client-local time? Is there a mechanism for that? It > seems to me that would be a logical benefit of the client having its > own view of the namespace. You can do that, if you really want. Observe the following: : root; date Mon Nov 12 21:24:49 EST 2012 : root; bind /adm/timezone/US_Hawaii /adm/timezone/local : root; date Mon Nov 12 21:25:21 EST 2012 : root; cp /adm/timezone/local /env/timezone : root; date Mon Nov 12 16:25:30 HST 2012 (the bind isn't needed, you can copy directly; it's just there for = illustration) Note, however, that everything started before you do this will have the = old idea about the timezone. Personally, when I've been in that situation, = I've found the cost of getting confused between, say, what a log file says versus what 'date' says to be more problematic than just remembering = that I'm (virtually) in Japan. Anthony