On 2014-01-16 19:59, Achim Gratz wrote:
Ever since systemd took over it waits for ntp to complete startup, which takes a long time on my machine. Is there any way I can make systemd start ntp, but not wait for it before it considers bringing up kdm?
I think it is intentional to wait. When eventually ntp service syncs, the clock can jump ahead or backwards, hopefully by less than a second if the cmos clock is not off by much, but eventually by minutes or hours. Some of the Linux services that are started after ntp can react badly to clock changes. I know of at least one (dovecot) that bails out if the clock goes back. It simply crashes nicely, with a message as to the reason. Of course, if you have no network you should disable or remove ntp. Or find out why it starts slowly. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)