hi admins,
sorry that, I did not type the "subject" in my previous mail.
sorrily
ram
> hi
>
> I got a number of response for the question. I have summarised few of
them.
>
> Overall, many suggested to use "ntp" or "rdate". Unfortunagely there is
no
> "rdate" on Irix. Also, using ntp means, I need to download the software
and
> configure.............
>
> the easiest way suggested is to use "timeslave" on Irix as pointed out by
> both :
>
> "Schultz, Juergen" <Juergen.Schultz@m.dasa.de>
> "Lothar Mueller" <mueller@darmstadt.gmd.de>
>
> (thanks to both of them.)
>
> cheers & smiles
> ram
>
>
> Responses
> ----------
>
> Mark Hargrave E-Mail: hargrme@wisdom.maf.nasa.gov
>
> > I use a freeware program called "ntpdate". It's sorta like "rdate".
> > > I put it in cron as follows:
> > >
> > > 37 2,8,14,20 * * * /usr/freeware/bin/ntpdate -u time.nist.gov
> > ntp.nasa.gov >/dev/null 2>&1
>
> -------------------------------
>
> You can synchronize your servers and all the PCs on your LAN for that
> matter
> to a network time server that is seperate from you server. IRIX
supports
> a
> protocol called NTP or XNTP. Odetics Telecom makes a product called
> NTPSync that connects to your LAN via a 10BaseT connection or through an
> AUI
> port. It supports version 1,2,3 of NTP. Once connected all you do is
set
> it up through the RS-232 port or IP address and set it as your primary
> time
> server. The advantages of this device are that it synchronizes your LAN
> time to a legally traceable time source using GPS Signals and it is an
> independent device. You can put two of them for redundancy. The price
is
> US1950 List and will be available in Mid May. It is not on the web site
> yet
> but I can mail you a catalog if you would like.
>
> Ken Sandfeld
> Director of Sales & Marketing
> Odetics Telecom "Timing is everything"
> 1585 S. Manchester Ave.
> Anaheim, CA 92802
>
> MAIN 714-780-7685 Toll Free 800-374-4783
> Direct 714-780-7684 Fax 714-780-7696
>
> e-mail: kps@odetics.com
> web: www.odetics-telecom.com
> ----------------------------------------
>
> "Schultz, Juergen" <Juergen.Schultz@m.dasa.de>
>
>
> I had this kind of problem recently. I solved the problem with using
> timeslave instead of timed. In case of using timed the clocks differed 3
> sec
> in 8min when using timed.
>
> To setup timeslave (which requests less cpu and network bandwidth) you
> have
> to set "chkconfig timeslave on" on your command line and set "-H
> <sunserver>" in the file /etc/config/timeslave.options which does not
> exist
> by default. You can set this on one machne and let the other SGIs be
> timed-connected to this machine.
>
> Then just start timeslave with "timeslave -H <sunserver>" and everything
> should be fine. When you just have a SGI machine with the time set
> correctly
> it is better to use this machine as timeserver. Do not ask me why, it's
> just
> experience.
>
> ---------------------------------------------------
> "Lothar Mueller" <mueller@darmstadt.gmd.de>
>
>
> We use timeslave on the SGIs.
>
> /usr/etc/timeslave -r 60 -H Sun-timeserver
>
> --------------------------------------------------
>
> > My original Question:
>
> > hi
> >
> > I have a IRIX client (IRIX Release 5.2) talking to SUN solaris server
> > (solaris 2.5.1). There is a time lag between the client and the
server.
> >
> >
> > I would like to synchronize the clock on the client with that of
> > server.
> >
> > I have plans for writing a script and reset the time on the client
> > every
> > hour or so.
> >
> > Is there any other better way of syncing the clocks..?
> >
> > ram
>
>
>
>
> _______________________________________________________
> Get your free, private email at http://mail.excite.com/
_______________________________________________________
Get your free, private email at http://mail.excite.com/
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:18 CDT