On 11/12/12, Phineas Pett <phineas.p...@gmail.com> wrote: > On 11/12/12, John Floren <j...@jfloren.net> wrote: >> On Mon, Nov 12, 2012 at 5:33 PM, Phineas Pett <phineas.p...@gmail.com> >> wrote: >>> Hello List, >>> >>> I'm attempting to setup a native Plan 9 system for the first time, but >>> I'm having a bit of trouble getting the timezone to ``stick.'' >>> >>> Putting the following in my /lib/profile seemed the intuitive and >>> correct thing to do: >>> >>> bind /adm/timezone/US_Central /adm/timezone/local >>> >>> But it does not work, and I don't understand why. >> >> I wouldn't expect this to work. According to date(1), >> /adm/timezone/local is copied into /env/timezone by init, meaning your >> bind comes far too late. > > 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. >
Ok thanks to both of you! I may have been too hasty responding earlier, I apologize for that. Running a single aux/timesync process from profile now keeps the clock steadily set. And a simple cat /adm/timezone/[timezone] > /env/timezone in the profile can set an arbitrary timezone locally. Phineas
