Xref: utzoo comp.unix.sysv386:8951 comp.unix.wizards:25966
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnews!junk1
From: junk1@cbnews.cb.att.com (eric.a.olson)
Newsgroups: comp.unix.sysv386,comp.unix.wizards
Subject: Network Time-keeping
Message-ID: <1991Jun14.024635.15860@cbnews.cb.att.com>
Date: 14 Jun 91 02:46:35 GMT
Organization: AT&T Bell Laboratories
Lines: 16


    I maintain a couple of dozen 386/486s networked
    together with RFS and use nmake viewpathing.   The current
    reference area(s) might be on another machine.  I am capable
    of syncing any machine to a common machine's time in seconds,
    using tools I have found here and within AT&T.  However, no matter
    how often I sync, it is not often enough to satisfy nmake.
    In fact, more frequent sync seem to force recompiles more often.
    A newer version of nmake will allow me to fudge the time within
    a few seconds; however, this newer version has semantic differences
    which make my current makefiles incompatible.

    Is there a version of the network time protocol available
    for TLI/streams?   I suspect that if I could sync them to milliseconds
    rather than seconds, it might work.   Anybody else have any thoughts
    on this?