X-Popmail-Charset: English
Newsgroups: bit.listserv.novell
Date:         Thu, 13 Aug 1992 13:11:10 +1000
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Brad Willcott <brad@POP.CC.ADFA.OZ.AU>
Subject:      Re: Login script, time synchronization source (LONGISH)
X-To:         JLW%PSULIAS.BITNET@SUVM.SYR.EDU, novell@suvm.syr.edu

On Thu, 6 Aug 1992 11:09:00 EST,
  J.Lance Wilkinson, 814-865-1818 writes:

>I just pulled and unzipped LOG365.ZIP from ftp.novell.com, and began reading
>the .DOC file distributed with it.  Among other things, it discusses a new
>script item in the 3.65 version of LOGIN, SET_TIME {ON | OFF}, which permits
>suppression (or acceptance) of the normal workstation/file server time
>synchronization performed by LOGIN.

Suggestion One:

In the system login script for the errant server, use the SET TIME OFF
command.

>I have four servers, one of which is notorious for loosing time, sometimes
>several minutes in a day.  Is there any way I could, during the system login
>script, synchronize from *one of the other servers*  instead of this one, if
>the user is logging into the one with the bad clock?  Our operations staff is
>supposed to reset the time on this bad clock'd server every night, but weekends
>mean two nights without operations stafffs, and every once in a while the night
>operator is too busy with other critical tasks to fix the time on an errant
>server.

Suggestion Two:

I wish assume that you are using NW3.11.

Get a copy of "311PT7.ZIP" from a novlib ftp site, and install the NLM
patches.  There is one that I think relates directly to your problem.  The
following is an exerpt from the doc file found in the archive:

---------------------------------------------------------------------
SYNCTIME NLM
2131 12-17-91   4:17p   This patch forces the server's date/time
                        to be synchronized to the hardware's
                        clock at specified intervals.  These
                        NLM's eliminate the gradual loss of time
                        experienced by the server due to "missed"
                        clock ticks while the server is in real
                        mode.

**NOTE: This file supersedes SYNC311.NLM(9-27-91 1987) previously
distributed under the name TIM386.ZIP in the NSD area of Netwire.

**NOTE ALSO: This file should not be confused with TIM386.ZIP
located in forum NOVLIB, Library 4, which is for Netware 386 v3.10a
and specifically refers to v3.10a in the documentation that comes
with that file.
---------------------------------------------------------------------

>Barring this, is there any program out there that will synchronize the
clocks
>on various servers?  Maybe one that would query a set of servers for times,
>determine the majority's timestamp, and set a (possibly different) set of
>servers to the time recognized by the majority...

I too would be interested in such a program/NLM.  Perhaps if someone knows
of one, he/she might 'speek up'?

Brad.
----------------------
Brad Willcott,                      Internet:   brad@pop.cc.adfa.oz.au
Computing Services,                 UUCP:!uunet!munnari.oz.au!pop.adfa.oz!brad
Australian Defence Force Academy,   +61 6 268 8163  +61 6 268 8150 (Fax)
Northcott Dr. Campbell ACT Australia 2600
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU