Tim,

Comments interspersed below...

Tim Bradshaw wrote:
>
> * ohaya wrote:
>
> > We tried to set this up yesterday, and got the xnptd running on all 4
> > machines, but when we tested, it didn't seem that anything was happening
> > (we ran snoops on port 123 on several of the machines).
>
> If you're not seeing any traffic on port 123 then I think ntp isn't
> running (or isn't doing anything)

With the new, simpler configurations that John Howells described earlier
in this thread, I am now seeing traffic regularly when I do snoop. It
looks like the 'client' end is sending out something every minute or so.



> > We tested by first using ntpdate on Solaris2, 3, and 4 to get them
> > synched to Solaris1, then starting the xnptd on those machines, then
> > setting the system clock on Solaris1 back about 10 minutes, and then
> > watching the snoop output for awhile.
>
> But you shouldn't do this! ntp is for dealing with clock drift, it's
> not designed to deal with massive changes in time. I can't remember
> what happens in cases like this but in at least some cases the clients
> will just log something to the effect of `I'm not going to try to fix
> that because it's too large an offset' and do nothing.


Thanks. I am now aware of that (no big changes). What I've done now on
the client end is to do a ntpdate to synch the client to solaris1, and
then starting xntpd. It now seems to be working as expected.

Thanks again,
Jim