Comment # 41 on bug 1145193 from
(In reply to Fabian Vogt from comment #37)
> I see there has not been any progress on this. I'm still very much in favor
> of reverting the change in YaST ASAP. The stream of incoming complaints
> about TW being unusuable is constant and we're losing users because of this.
> 
> Fixing this in a way that everyone can agree on can be done afterwards.

Yes, please!

I agree with Thorsten that there is much stuff to be fixed in this area, but
just enabling chrony-wait.service through YaST and ignoring the other problems
this brings up was throwing out the baby with the bath water.

Maybe for the time being the default-enablement of chrony-wait.service can be
done in a way so that it only happens on openSUSE Kubic, but not on normal
Tumbleweed? If not, let's disable it by default until the followup-problems
have been sorted out.

(In reply to Josef Reidinger from comment #40)

> what change in YaST you have mean? Switch from ntpd to chrony? Or something
> else?

The fact that YaST enables chrony-wait.service as a result of bug #1137196.


You are receiving this mail because: