I'm sure Redhat has implemented some services of type Simple.
However, my service is oneshot, and what you're saying is there's no way for me to force any other service to wait until my service exits before bootup continues?
This doesn't seem right given that systemd can wait for a password to unlock encrypted volumes.
From: systemd-devel <email@example.com> On Behalf Of Reindl Harald
Sent: Monday, December 10, 2018 3:42 PM
Subject: EXT :Re: [systemd-devel] Systemd dependencies
Post by Boyce, Kevin P [US] (AS)
I seem to be struggling with what should be a very basic operation.
I’ve seen similar questions posted to the list here and none of them
are really adequate.
I’m trying to prompt the user to ask a question as the system is
coming up (so the system can configure it’s network and other things
based on a hostname the user enters).
I have this part working using system-ask-password which is executed
using a oneshot/idle service unit. However before the user can enter
their response on the console the graphic display starts up. In the
unit file I’ve tried all sorts of combinations of Requires, After,
WantedBy, RequiredBy, etc. to make the graphical.target happen only
after this script has completed its execution to no avail.
Any help would be appreciated. I’ve thought of creating a new custom
target and putting my service in it. Is there a way to force another
target not to start until another target is completely finished?
Just wondering why this sort of operation is so hard.
because you likely have some "Type=simple" stuff instead foking/notify which don't ait for anything in your chain and no additional targets can fix that _______________________________________________
systemd-devel mailing list