NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/os/vms/20526

Internet Message Format | 1993-01-07 | 1.5 KB

Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!linac!att!ucbvax!mhs.attmail.com!simons/G=Colin/I=CB/S=Sewell/O=H.A.Simons.Ltd/OU=CORP
From: simons/G=Colin/I=CB/S=Sewell/O=H.A.Simons.Ltd/OU=[e-mail]
Newsgroups: comp.os.vms
Subject: Re: Date incorrect after reboot
Message-ID: <[e-mail]>
Date: 7 Jan 93 16:52:12 GMT
Sender: [e-mail]
Organization: The Internet
Lines: 27

Rob W.W. Hooft writes:
!Just make sure you have a cluster: good LAVC practice is to
!synchronize the clocks every once in a while: I think SET TIME/CLUSTER
!will also take care of the problem?
!
!And: NO: Our VAX systems NEVER crash. Uptimes upto 600 days, causing an
!overflow in the CPU time of the NULL process (Yes: VMS 4.7).

    to get really reliable time synchronization across all nodes
    in a LAN/WAN, split the DTSS server and client software off
    of the DECNET/VAX Extensions V5.4 distribution. We have this
    software running on all nodes in our network and even have
    a time provider routine that dials up the NBS-ACTS time
    service occasionally and coordinates with universal time. The
    time provider time is synched across all nodes of our network
    and the time is rarely off more than a fraction of a second
    on all nodes. DTSS even handles differing timezones and will
    even change your clock automatically on DST changes.

    And all it requires is a DECnet license to run. You don't even need
    DNS or to install DNVEXT.

    colin sewell
    h.a.simons ltd.
    vancouver, bc
    "simons/g=colin/s=sewell"@mhs.attmail.com