thx for the answer. 

> If you do not use "--no-block" to start your second target, first
> target will never finish.

That's something I cannot confirm. If you define the service, which is calling 
"systemctl start xxx", as oneshot the service will be in state activating for 
exactly the time needed to bring up the target.

> Other caveat of your way is that systemd doesn't know about your final
> target until it receives "systemctl start destination.target". Since it
> doesn't know about the target, units that are requested by
> destination.target will not have the default dependencies applied.

That's true but wanted in my case ;)

Best regards

Marko Hoyer
Software Group II (ADITG/SW2)

Tel. +49 5121 49 6948
systemd-devel mailing list

Reply via email to