[EMAIL PROTECTED] wrote:
> I'm trying to configure NTP for a cluster. The cluster has a "master"
> node and all nodes know which node is master. My NTP configuration is
> to have the master node the only node that contacts an external NTP
> server, with the other nodes using the master as their tim
Ryan Malayter wrote:
> On Apr 2, 8:17 am, [EMAIL PROTECTED] (Per Jessen) wrote:
>> In my opinion, your elaborate scheme of running ntpdate here and there
>> is far more work and far more convoluted.
>
> Would you recommend the same thing for a laptop, which periodically
> sleeps and is is periodic
I'm trying to configure NTP for a cluster. The cluster has a "master"
node and all nodes know which node is master. My NTP configuration is
to have the master node the only node that contacts an external NTP
server, with the other nodes using the master as their time server.
The master node's ntp.
>>> 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
>I'd like to know something like this: If we assume the servers are
>reasonably accurate, and state the statistics of the network jitter and the
>behaviour of the client oscillator, and control the clock using NTP over the
>network, what frequency variation can we expect?
It's probably more compl
Can anyone point me to some simulations that indicate the accuracy
achievable using NTP?
I'd like to know something like this: If we assume the servers are
reasonably accurate, and state the statistics of the network jitter and the
behaviour of the client oscillator, and control the clock using NT
On Apr 3, 12:00 pm, Steve Kostecke <[EMAIL PROTECTED]> wrote:
> (a) Restart ntpd in your suspend/resume and network state change scripts
Does anyone know if (a) as described above a default configuration in
many Linux/BSD distributions? It doesn't seem to be configured this
way with the ntp-server
10 matches
Mail list logo
