В Sat, 12 Jan 2013 11:28:01 -0600
Michael Catanzaro
On Sat, 2013-01-12 at 09:07 -0600, Rajko wrote:
On Sat, 12 Jan 2013 14:48:00 +0100 "Carlos E. R."
wrote: It is clearly documented that non-standard init scripts are not supported and will never be.
That is an unaceptable support regression.
It is not.
There's no sense in debating this since systemd is already here to stay - now we have to make it work. If ntpd can be made to work fine with an initscript then great; if not it needs to be fixed. And right now it needs fixed.
timedated and timedatectl would be nice if they worked - right now they're broken. (If you check the source, it's expecting to find an ntp unit file - which is not exactly an unreasonable expectation, though something that could be patched if that'd be easier than providing a unit.
What is wrong with adding unit that calls initscript? This will fix timedated NTP information and leave time to work on native ntpd.service implementation.
Though maybe something else is wrong too.)
Yes, on 12.2 timezone information is wrong. timedated takes it from /etc/timezone which does not exits. You can of course create it, but will not be kept in sync by YaST2. Current upstream systemd dropped this and simply assumes /etc/localtime is always a link to correct timezone file. I do not know whether a) version in 12.3 already have this change b) YaST2 12.3 is modified to create link. /etc/localtime is plain file on 12.2.
Also, and this particular point is not really related to systemd but it's important enough to mention - NTP is by default broken regardless.
One problem that seems to be totally ignored is https://bugzilla.novell.com/show_bug.cgi?id=791106 Many people are affected, and it severely breaks dual boot with Windows.