On Tue, Jan 22, 2013 at 07:29:43PM -0500, Alon Bar-Lev wrote:
This is nice to know....
otopi is ready:
commit d756b789d60934f935718ff25f8208f563b0f123 Author: Alon Bar-Lev <alonbl@redhat.com> Date: Wed Jan 23 02:27:51 2013 +0200
system: clock: support chrony as ntpd
Change-Id: I2917bdd8248eb0b123f6b2cca875820f2cac664c Signed-off-by: Alon Bar-Lev <alonbl@redhat.com>
Alon, if both ntpq and chronyc are installed, do you intentionally run them both?
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Dan Kenigsberg" <danken@redhat.com> Cc: "Adam Litke" <agl@us.ibm.com>, "Alon Bar-Lev" <alonbl@redhat.com>, "users" <users@ovirt.org> Sent: Wednesday, January 23, 2013 1:50:59 AM Subject: Re: [Users] host deploy and after reboot not responsive
On Tue, Jan 22, 2013 at 9:02 PM, Dan Kenigsberg wrote:
That's great, as it reduces the question to: why doesn't ntpd start on your machine after boot. Do you have any guess? and ntpd logs to share? Any peculiar ntp.conf setting?
Hum... I think in Fedora 18 itself and/or due to oVirt setup there is some conflict regarding network synchronization services....
In fact together with standard ntp there is chrony that I didn't know until today...
My suspect is this one:
- At install time Fedora 18 by default installs now chrony and doesn't install instead ntpd
Gianluca, how about softening our ntpd requirement with something like http://gerrit.ovirt.org/11291 ? Could you verify that it's working on your system?