Comment 11 for bug 90524

@schmirrwurst:

yes, this is why I suggested looking at the other bug. I do not see an immediate, simple solution here. Of course, NTP's approach to correcting the clock seems sensible and good, but some users want the clock corrected NOW, and this approach (I mean NTP's) may simply not do the trick here.

Also, "synchronise now" does not make sense when NTP is running (since only ntpdate can do it) -- and, at the same time, will potentially confuse a lot of users. On the other hand, the default behaviour of ntpd is to step differences bigger than ~ 100 ms -- which means instantaneous correction, so this is no big deal, unless you really need your clock accurate to the 10s of ms.

I think this will have to be worked out on discussions by the developers.