[systemd-devel] bug or I misunderstand systemd configuration rules ?

[小蔡]

On 2011年08月26日 03:33, Warpme wrote:
> Hi,
>
> I have problem with understanding following systemd behaviour and need
> assistance of somebody knowledgeable in systemd config area:
>
> Context:
> daemon1 is server for application1
>
> 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

> 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.

> 5\abort of daemon1 triggers also restart of application1
daemon1 will be started again.

>
> I do tests on ArchLinux with systemd 33.
>
> For daemon1 unit file I don't enter any relevant to this example
> After/BindTo statements.
>
> For application1 unit file I have:
>
> [Unit]
> After=deamon1.service
> BindTo=daemon1.service
>
> Above configuration work as expected for 1\, 2\ & 3\
> AFAIK 5\ is not Yet implemented.
> Unfortunately for 4\ systemctl hangs during execution "systemctl
> restart daemon1".
>
> It is bug or I completely misunderstand systemd configuration rules ?
>
> br
>
>
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110826/13bd33f9/attachment.htm>