@Richard
I know that one shapshot is very early on but if you look at the start of the
thread you can see information on what things look like after it has been
running a while and in that second output of the two in that last post you can
see that it is quickly headed in that direction after
Chris Albertson wrote:
If you are on an isolated network a better setup is to put three
SERVER lines in each config file where each of the tree computers has
itself and the other two to select from. ntp will find the best clock
That's a recipe for disaster. If you are a rime island and you
Robert Hegner wrote:
Can W32time act as a server for the Meinberg NTP version on my other
computers? Is there a special configuration needed for this to work?
With my unmodified config files on 192.168.0.2 and 192.168.0.3, these
computers don't reach a time server on 192.168.0.1.
Modern
Can it even be fixed?
Well I hope so. Not to bash on the linux world, but I don't get why this
timing thing is so hard... I mean I understand it from a techinical
perspective because I've read all about how the hardware and timers and stuff
work, but practically speaking, somebody needs
Yes this is a VM (see other ealier posts about that). I've been trying to get
the clock to behave but haven't found the solution. Some people seem to think
there isn't an answer. I'm not after super accurate time here, I just want my
clock to stay within a minute or two of what actual time
Robert Hegner wrote:
The configuration file for 192.168.0.1 contains the following two lines:
server 127.127.1.1
fudge 127.127.1.1 stratum 1
This stratum is considered bad practice. If the machine had actually
been having its clock disciplined externally to true UTC time, the
stratum 6 in
Any idea how to get a clock correction on a MS Virtual PC / Virtual Server?
Last time I tried to install the MS VPC tools for linux on a machine it
thoroughly hosed things up; so unless there is a new an improved version I'm a
little hesitant to go there agian.
Chris Albertson wrote:
On Mon, Feb 28, 2011 at 11:10 PM, Robert Hegner robert.heg...@hsr.ch wrote:
domain policies do not allow the NTP service to set the time.
That needs to be fixed. Kill the service that sets the time. NTP can
not coexist with another program that sets the local clock.
David wrote:
The configuration file for 192.168.0.1 contains the following two lines:
server 127.127.1.1
fudge 127.127.1.1 stratum 1
This stratum is considered bad practice. If the machine had actually
been having its clock disciplined externally to true UTC time, the
stratum 6
Ralph wrote:
Can it even be fixed?
Well I hope so. Not to bash on the linux world, but I don't get why this
timing thing is so hard... I mean I understand it from a techinical
perspective because I've read all about how the hardware and timers and stuff
work, but practically speaking,
Hi all
[]
Robert
Robert,
You have had some good advice from other here. I have various Windows
systems here running NTP, with offsets of less than 100 microseconds
(Windows-7, PC Stamsund, with an attached GPS/PPS device) and less than 1
millisecond (Windows XP, PC Narvik, LAN-synced).
David Woolley wrote:
Chris Albertson wrote:
If you are on an isolated network a better setup is to put three
SERVER lines in each config file where each of the tree computers has
itself and the other two to select from. ntp will find the best clock
That's a recipe for disaster. If you are a
On 3/6/2011 4:48 PM, Chris Albertson wrote:
On Sun, Mar 6, 2011 at 12:18 PM, Ralphra...@depth.net wrote:
It is a VM, which I'm sure is why the clock isn't playing nice but I haven't
found the right solution to fix it..
Can it even be fixed? I'd guess maybe not. Has anyone here run ntpd
On 3/7/2011 3:00 AM, Ralph wrote:
Yes this is a VM (see other ealier posts about that). I've been
trying to get the clock to behave but haven't found the solution.
Some people seem to think there isn't an answer. I'm not after super
accurate time here, I just want my clock to stay within a
On 2011-03-06, Ralph ra...@depth.net wrote:
It is a VM, which I'm sure is why the clock isn't playing nice but I haven't
found the right solution to fix it... The clock was running fast until I
added the divider=10 option and now it runs slow - but I rather have ntp have
to move the clock
On 2011-03-07, Ralph ra...@depth.net wrote:
Can it even be fixed?
Well I hope so. Not to bash on the linux world, but I don't get why this
timing thing is so hard... I mean I understand it from a techinical
perspective because I've read all about how the hardware and timers and stuff
Ralph wrote:
Not to bash on the linux world, but I don't get why this
timing thing is so hard...
I mean I understand it from a techinical perspective
because I've read all about how the hardware and timers
and stuff work, but practically speaking,
somebody needs to get with the program
Ralph wrote:
Can it even be fixed?
Well I hope so. Not to bash on the linux world, but I don't get why this
timing thing is so
hard... I mean I understand it from a techinical perspective because I've read
all about how the
hardware and timers and stuff work, but practically speaking,
Terje Mathisen wrote:
David Woolley wrote:
Chris Albertson wrote:
If you are on an isolated network a better setup is to put three
SERVER lines in each config file where each of the tree computers has
itself and the other two to select from. ntp will find the best clock
That's a recipe for
On Mon, Mar 7, 2011 at 2:11 PM, David Woolley
david@ex.djwhome.demon.invalid wrote:
Terje Mathisen wrote:
David Woolley wrote:
Chris Albertson wrote:
If you are on an isolated network a better setup is to put three
SERVER lines in each config file where each of the tree computers has
20 matches
Mail list logo
