Hi Lennart,
Thank you for your reply.
Is there a way to execute stop actually, even the status is inactive.
------------------ ???????? ------------------
??????: "Lennart Poettering"<lenn...@poettering.net>;
????????: 2017??6??27??(??????) ????3:29
??????: "????"<624001...@qq.com>;
????: "systemd-devel"<systemd-devel@lists.freedesktop.org>;
????: Re: [systemd-devel] systemctl can't execute stop actually, whenservice is
started by other way
On Tue, 27.06.17 13:48, ???? (624001...@qq.com) wrote:
> for example: service nscd
> 1.execute: systemctl stop nscd.service
> stop nscd process actually
> 2.execute: /usr/bin/nscd
> start nscd by shell command
> 3.execute: systemctl status nscd.service
> inactive(dead)
> systemctl can't know nscd is running
> 4.excute: systemctl stop nscd.service
> nscd process still exist, it seems that systemctl does not execute stop
> actually
>
>
> How can I stop nscd.service by systemctl when it is started not by
> systemctl?
You cannot. systemd is a service manager. When you tell it to manage
something that means it will start/stop/introspect/... it for you. But
if you manage the service on your own, outside of it, then it won't do
any of that.
Hence: either let systemd the service and then also stop it for you,
or do it yourself, but you cannot let it stop it for you but not start
it in the first place.
Sorry,
Lennart
--
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
