Linda Walsh writes:
I thought you said it was when the ntp start up script ran?
Exactly.
and that you tried both with and without the "chroot" with same result.
Yes.
With that, the only thing the startup script should be doing is running the ntp daemon.
You'd think, but it's not that. I've ran the actual invocation by hand and never observed anything unusual.
This type of script is what is missing in "systemd" -- that makes it hard to debug problems like these, BTW, so going back to an earlier suse version to pull out the start scripts is a good start-point for seeing what systemd "should" be doing.
Since it "hangs" more than two minutes on boot, I was able to log in on the console and see what was running and what caught my eye was systemctl status ntp So I added "set -x" to the init script and ran it again after KDE started (this is where it takes again two minutes) and it hung at the exact same command, more specifically when it was trying to list the log related to ntp (long after it had already determined the status of the daemon). So I wasn't seeing ghosts after all and this is indeed caused by systemd and it's "improved" way of dealing with system logging. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org