[systemd-devel] systemctl how to stop a service

[Reindl Harald]

Am 16.05.2016 um 08:58 schrieb Andrei Borzenkov:
> 16.05.2016 09:01, liuxueping пишет:
>> Do you mean to say that systemctl will return a value when the process
>> is still at terminate gracefully?
>>
>
> By default systemctl should wait for stop job to complete. What may
> happen - if it takes more time than JobTimeout, job is canceled while
> systemd is still trying to terminate unit. At least so is my understanding

IT DON'T RELIEABLE - my harddisks still making a lot of nosie by 
suspending 3 VMware guests on a RAOD10 with 4 different disks and i have 
observed similar behavior for single services too

[root at srv-rhsoft:~]$ time systemctl stop vmware-guest.target
real    0m2.484s
user    0m0.007s
sys     0m0.010s

[root at srv-rhsoft:~]$ systemctl status vmware-guest.target
vmware-guest.target - VMware Guest Group
    Loaded: loaded (/etc/systemd/system/vmware-guest.target; enabled; 
vendor preset: disabled)
    Active: inactive (dead) since Mo 2016-05-16 12:25:18 CEST; 1min 19s ago

Mai 16 12:25:18 srv-rhsoft.rhsoft.net systemd[1]: Stopped target VMware 
Guest Group.
Mai 16 12:25:18 srv-rhsoft.rhsoft.net systemd[1]: Stopping VMware Guest 
Group.
Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.


>> 在 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   08:45   0:00 [ntpd]
>
> I'm not sure how to interpret it. For one, it has [...] in name which
> indicates it is kernel thread. I am not aware that ntpd starts any
> kernel threads and if it does, systemd does not monitor them in any
> case. So /if/ this is kernel thread, the result is expected.
>
>>>> After 5 seconds,there is no ntpd process in system.
>>>>
>>>> the stop status is 0,the execution of the stop command is successful,the
>>>> PID of the ntpd process is 1.
>>>>
>>>> I would like to know if the systemctl command will wait for all the
>>>> processes to exit completely before returning the result
>>>
>>> no, not relieable, had much fun with maradb-backups
>>>
>>> in case of restart it's different but "stop" is mostly a fire and forget
>>> coming back in the terminal whil the daemon is still at terminate
>>> gracefully - IMHO a bug
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> systemd-devel mailing list
>>> systemd-devel at lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>>
>>
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>

-- 

Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / CISO / Software-Development
m: +43 (676) 40 221 40, p: +43 (1) 595 3999 33
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160516/1770a58e/attachment-0001.sig>