Am 13.01.2013 22:57, schrieb Paul Wouters: > On 01/12/2013 04:33 PM, Zbigniew Jędrzejewski-Szmek wrote: >> On Fri, Jan 11, 2013 at 08:20:45PM +0100, Reindl Harald wrote: >>> >>> >>> Am 11.01.2013 19:47, schrieb Paul Wouters: >>>> So the daemon restarts all the time. So let's tell systemd to disable >>>> it, while leaving the service running: >>>> >>>> [root@west ~]# systemctl disable ipsec.service >>>> [root@west ~]# pidof pluto >>>> 1992 >>>> [root@west ~]# killall -9 pluto >>>> [root@west ~]# pidof pluto >>>> 2095 >>>> >>>> So I guess the man page is either lying or the disasble command is not >>>> working as expected. > >> The part that you quoted even explicitly says that 'systemctl disable' >> has no effect on the running system! > > I interpreted that as "from now on, systemd will not restart the service, but > it will not stop the running > service". So that when I manually killed the daemon, I expected it to _not_ > start it.....
stop a daemon = systemctl stop that is really easy to understand kill outside of systemctl is "hmm dameon has gone way and i was told to restart" this is really really easy what is not so easy and broken by desing is that "systemctl stop wahterver.service" on a service with a systemd-socket triggers to get the service started again if something try to access the port
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
