Oh, I don't want to be too principal, but You miss whole point. 5 cases listed by me are not list of observed results but rather list of expected behavior...
>> I want to have situation where: >> 1\"systemctl start application1" also starts daemon1 >Yes >> 2\"systemctl stop daemon1" also stops also application1 >No, daemon1 will be started as long as application1 talk to daemon1 Not so obvious. I'm not using any socket systemd functionalities, so correlation mechanism between daemon1 & application1 is based exclusively on systemd internal state machine driven by process state related events. >> 3\"systemctl restart appication1" restarts only application1 >yes >> 4\"systemctl restart daemon1" restarts also application1 >No need to do that. Just restart daemon1 and application1 won't even >notice that. Might be not true. This is purely application1 depended thing and there is set of application which needs to be restarted when serving them daemon1 was restated (as they don't have build-in auto-concretion mechanism). -br _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
