В Mon, 16 Mar 2015 15:27:05 +0100
Marcus Meissner
On Mon, Mar 16, 2015 at 03:25:21PM +0100, Per Jessen wrote:
After killing a wrongly started ntpd, I tried starting a new one:
systemctl start ntpd
This seems to hang:
4 0 1163 1 20 0 45216 4996 core_s Ss ? 0:00 /usr/sbin/sshd -D 4 0 2974 1163 20 0 81640 6060 core_s Ss ? 0:00 \_ sshd: root@pts/4 4 0 2981 2974 20 0 14724 4600 wait Ss pts/4 0:00 | \_ -bash 4 0 8128 2981 20 0 24552 2824 SyS_pp S+ pts/4 0:00 | \_ systemctl start ntpd 0 0 8129 8128 20 0 13160 1664 SyS_po S+ pts/4 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch
Sofar it's been waiting about 3 minutes. What is it waiting for?
I think it waits for a password.
No, it monitors for password requests (from *any* service, not necessarily one that is being started); if any request is posted, it will ask for password on /dev/tty. systemctl requests are synchronous by default and wait until job completes or times out. As indicated by message in another post, systemd is waiting for ntpd.service to be restarted. ntpd.service has Restart=always and RestartSec=11min. To force service to be started before RestartSec is elapsed use "systemctl restart", not "systemctl start". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org