If it is as you say,it takes more time than JobTimeout,job is canceled
while systemd is still trying to terminate unit,then the return value
should not be 0.
在 2016/5/16 14:58, Andrei Borzenkov 写道:
16.05.2016 09:01, liuxueping пишет:
Do you mean to say that systemctl will return a value
Do you mean to say that systemctl will return a value when the process
is still at terminate gracefully?
在 2016/5/14 18:32, Reindl Harald 写道:
Am 14.05.2016 um 10:55 schrieb liuxueping:
The result of "ps aux" before sleep 5 shows:
root 6698 0.0 0.0 0 0 ?Ds
Hi:
I have a test in arm64,my test case try to start/stop a ntp service
frequently,like that:
#!/bin/bash
i=0
while [ 1 ];do
echo "$((i++))"
systemctl restart ntpd &
kill -9 $!
sleep 10
systemctl stop ntpd
echo "stop status:$?"
systemctl start ntpd
ps aux >> file
schrieb liuxueping:
Before i restart ntpd,ntpd process was running:
ntp 3993 0.0 0.0 7404 4156 ?Ss 10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
root 3995 0.0 0.0 7404 2364 ?S10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
so,it should be killed by systemctl
process,but
it failed,i want to know systemd how to judge that a process is killed
completed to start a new service.
在 2016/5/12 16:51, Reindl Harald 写道:
Am 12.05.2016 um 09:17 schrieb liuxueping:
Hi:
It failed when i restarted ntpd service,the log showed:ntpd[3163]:
unable to bind
Hi:
It failed when i restarted ntpd service,the log showed:ntpd[3163]:
unable to bind to wildcard address 0.0.0.0 - another process may be
running - EXITING,and the ps command result showed:
ntp 3993 0.0 0.0 0 0 ?Ds 10:21 0:00 [ntpd]
root 3995 0.0 0.0 0
