In article <[EMAIL PROTECTED]>,
Richard B. gilbert <[EMAIL PROTECTED]> wrote:
> It's a little less than clear what you hoped to accomplish by this and
Making gross changes to the clock on a running machine is how people
think they can test that ntpd is synchronising the clock, when what they
sho
>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Christine Ross) writes:
Christine> I am setting up a solaris 8 server as an v3 ntp client (using
Christine> public ntp servers). I can change the date and time and then
Christine> start xntpd daemon with the start script and the time sets to
Christine Ross <[EMAIL PROTECTED]> wrote:
> I am setting up a solaris 8 server as an v3 ntp client (using public ntp
> servers). I can change the date and time and then start xntpd daemon with
> the start script and the time sets to the correct time.
>
> When I issue the "date" command, se
Christine Ross wrote:
> I am setting up a solaris 8 server as an v3 ntp client (using public ntp
> servers). I can change the date and time and then start xntpd daemon with
> the start script and the time sets to the correct time.
>
> When I issue the "date" command, setting the clock back
I am setting up a solaris 8 server as an v3 ntp client (using public ntp
servers). I can change the date and time and then start xntpd daemon with the
start script and the time sets to the correct time.
When I issue the "date" command, setting the clock back 10 minutes, the time
doesn't s