home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Date incorrect after reboot
- Date: 9 Jan 1993 13:38:43 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 21
- Distribution: world
- Message-ID: <1imkh3INNg7a@gap.caltech.edu>
- References: <1993Jan5.215635.6062@odin.corp.sgi.com> <61050106@acf3.NYU.EDU> <7JAN199314465903@spades.aces.com>,<17321.2b4d3808@bclcl1.im.battelle.org>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <17321.2b4d3808@bclcl1.im.battelle.org>, hansher@bclcl1.im.battelle.org (Kevin Hansher, Battelle Computing Center) writes:
- >If I am really interpreting correctly what is said here (i.e. that (b) is
- >not needed to be done in a cluster with a common system disk and system
- >image SYS.EXE), then I believe that information to not be true. I believe
- >this is exactly what causes one of the many time problems that are reported
- >at various sites.
-
- No. The problem under discussion results from the fact that VMS combines year
- information from SYS.EXE (sorry about incorrectly referring to SYSBOOT.EXE
- earlier) with the data in the TOY clock. Doing a SET TIME from *ANY* system
- sharing the common system disk updates the year information in SYS.EXE. The
- TOY clocks should not normally need to be updated, and if they *ARE* off,
- you'll find that you've got the wrong time/day-of-year, *NOT* the wrong year.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-