🚀 go-pugleaf

In article <1ck55uINNg7@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art  
Isbell) writes:
> 
> Did anyone else experience the failure of US/Pacific-New to change to  
PST
> correctly?   I set Preferences to US/Pacific and that seems to work,  
but will
> it work next spring?  Which is the proper Preferences setting for  
those of us
> in the US/Pacific time zone?

We have three NeXTs networked, all have Time Standard set on Automatic  
(NetMgr), all enabled as Clones for Time Service. On Sunday, the  
network server showed the correct PST time, while the other two--one of  
which is a clone server--still showed PDT. After fooling around with  
NetMgr and NetInfoMgr and whatall flat files, I finally noticed that  
the Preferences were set as US/Pacific on the server and US/Pacific-New  
on the other two. Once they were changed to US/Pacific, they showed  
PST. I don't know what US/Pacific-New or PPET is, but I'm avoiding it  
henceforth.
--
 
Eric Minch             Any resemblance to the opinions of persons
Epistemic Artisan      or organizations other than myself--living,
Stanford Genetics      dead, or imaginary--is purely fortuitous.