Hello,

I'd like to ask if systemctl isolate and systemctl start can be executed
together.

*Background*
A.target is the system's default.target. A.target is associated with
A.service, which executes A.sh. That is, systemd first executes A.sh after
booting.
A.sh switches to multi-user.target via systemctl isolate multi-user.target
in the final stage. The following statement immediately executes systemctl
start X.service. X.service has a default dependency on sysinit.target.


*A.sh*
>
>
>
> *...systemctl --no-block  isolate multi-user.targetsystemctl start
> X.service*


*Question*
Does this syntax potentially cause issues, such as systemd server timeouts
or job conflicts? Thanks.


Best regards,
Alien Kong

Reply via email to