http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c65 Reinhard Max changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(max@suse.com) | --- Comment #65 from Reinhard Max --- (In reply to Josef Reidinger from comment #64)

Reinhard - I test potential change in yast with proposing to default ntp server option "offline" which should mark source as offline and then network dispatcher can activate it ( e.g. NM in /etc/NetworkManager/dispatcher.d/20-chrony ). But sadly it does not work and it still waiting when I am testing it (instead of using rtc when all ntp servers are marked as offline).

I wouldn't expected that to work, because when no ntp servers are reachable the clock is unsynchronized and hence chrony-wait waits.

Enabling chrony-wait based on availability of network is also tricky as e.g. notebooks can have network when installed and then travelling without network.

Yes, I also won't recommend that.

So do you really see disabling chrony-wait as only option here for YaST how to short-term fix it?

Yes.

( of course plan is that we add option to control.xml if product require precise time and if so, then it will still enabled e.g. for Kubic ).

That's also only part of the workaround. It is services not products that require (or not) precise time, but until we have the dependencies sorted out to a point that we can enable chrony-wait unconditionally without blocking boot without network, it makes sense to enable it only on products that are usually not booted without network and have services that need precise time. -- You are receiving this mail because: You are on the CC list for the bug.