Re: [Users] host deploy and after reboot not responsive

----- Original Message ----- > From: "Dan Kenigsberg" <danken(a)redhat.com&gt; > To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; > Cc: "Alon Bar-Lev" <alonbl(a)redhat.com&gt;, "Adam Litke" <agl(a)us.ibm.com&gt;, "users" <users(a)ovirt.org&gt; > Sent: Wednesday, January 23, 2013 12:09:59 PM > Subject: Re: [Users] host deploy and after reboot not responsive > > On Wed, Jan 23, 2013 at 10:57:03AM +0100, Gianluca Cecchi wrote: > > On Wed, Jan 23, 2013 at 9:40 AM, Dan Kenigsberg wrote: > > > 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? > > > > Yes, I can test the change the service modification for vdsmd. > > I presume you want me to test it with default fedora 18, so chronyd > > enabled and ntpd disabled, correct? > > Yes. though my patch may generate excessive noise, with its attempt > to > start two conflicting service. I suppose that we can/should "want" > only > chrony. But please provide your input. We should use either, and default.

On none systemd other distributions there is the concept of 'provides'. This means that a service like vdsmd can depend on timesync and a service like chronyd *AND* ntpd provide timesync. This is kind of logical name for service. Also other non systemd distributions provides the ability to script the dependencies. I could not find either of he above methods in systemd documentation.