Your client software is five years out of date, I suggest you update
it.
Red Herring.
Not even worth updating for the security updates?
The problem here is that the client system is running in a VM.
Not mentioned in the original post, though!
The OP wants to sync this client to his
Chris Albertson albertson.ch...@gmail.com wrote:
3) I think you need more than one server line. What if 10.200.37.37
needs to be taken off-line. I'd set up at least two ntp servers and
configure al clients to use both
Of course now others will chime in that you need more than two, and in
the
You are right. It all depends on what you need. But notice that his
client was off by about an hour because it coud not contact his
server. Some system don't freewheel as well as others
On Wed, Apr 27, 2011 at 1:33 AM, Rob nom...@example.com wrote:
Chris Albertson albertson.ch...@gmail.com
Chris Albertson albertson.ch...@gmail.com wrote:
You are right. It all depends on what you need. But notice that his
client was off by about an hour because it coud not contact his
server. Some system don't freewheel as well as others
The reason that it was off was not that it could not
On 4/27/2011 11:14 AM, Chris Albertson wrote:
others will chime in that you need more than two, and in
the end you will need 9 servers or so.
But this is of course hogwash. You define what you need. When you
have one server and it is taken offline, the clients clocks will continue
to run
On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote:
Hi Steve,
Yes it is virtual machine, the host is linux also with vmware server
installed.
Stop trying to sync a virtual machine. It's clock cannot be relied on to
keep time.
Discipline the underlying clock.
Kinldy note
Dear Support,
I have a NTP server, and configure clients on it.
I am facing an issue that the offset is too much high so there a difference in
the time between the client and the server, it is reaching 1 hour sometimes.
NTP client version:
ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu
Dear Support,
This is a newsgroup, there is no support as such.
I have a NTP server, and configure clients on it.
I am facing an issue that the offset is too much high so there a
difference in
the time between the client and the server, it is reaching 1 hour
sometimes.
NTP client version:
On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote:
client machine : linux redhat 4.6
[root@dmtestapp1 ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
10.200.37.37
On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote:
Dear Support,
I have a NTP server, and configure clients on it.
I am facing an issue that the offset is too much high so there a difference in
the time between the client and the server, it is reaching 1 hour sometimes.
David wrote:
Dear Support,
This is a newsgroup, there is no support as such.
I have a NTP server, and configure clients on it.
I am facing an issue that the offset is too much high so there a
difference in
the time between the client and the server, it is reaching 1 hour
On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
Attribution Missing wrote:
ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT
2006 (1)
Your client software is five years out of date, I suggest you update it.
Red Herring.
remote refid
On Tue, Apr 26, 2011 at 1:32 PM, Steve Kostecke koste...@ntp.org wrote:
On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
Attribution Missing wrote:
ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT
2006 (1)
Your client software is five years out of
Steve Kostecke wrote:
The problem here is that the client system is running in a VM.
That's most likely, however the inappropriate use of the local clock
driver isn't helping, by making it virtually impossible for it even to
get by with infrequent time steps. Without that, either ntpd
On 2011-04-26, Steve Kostecke koste...@ntp.org wrote:
On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
Attribution Missing wrote:
ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT
2006 (1)
Your client software is five years out of date, I suggest
On Tue, Apr 26, 2011 at 3:01 PM, David Woolley
david@ex.djwhome.demon.invalid wrote:
Steve Kostecke wrote:
The problem here is that the client system is running in a VM.
That's most likely, however the inappropriate use of the local clock driver
isn't helping,
Just wondering how you
=damanhealth...@lists.ntp.org
[questions-bounces+yousif.qaddoura=damanhealth...@lists.ntp.org] On Behalf Of
Steve Kostecke [koste...@ntp.org]
Sent: Tuesday, April 26, 2011 6:56 PM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, Yousif Qaddoura yousif.qaddo
On 2011-04-26, unruh un...@wormhole.physics.ubc.ca wrote:
On 2011-04-26, Steve Kostecke koste...@ntp.org wrote:
On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid
wrote:
In your ntd.conf, remove the local clock, and add in three pool
server lines such as:
Yousif Qaddoura wrote:
Yes it is virtual machine, the host is linux also with
vmware server installed.
Kinldy note that the host machine's time is correct
and it is synchronizing with my NTP 10.200.37.37
Here are some links I've run across in the past related
to VMware NTP. You'll likely
19 matches
Mail list logo