[systemd-devel] Check for plymouth (e1b2b49465615727a2c3883d06d1b9ff339aec67)

[Andrey Borzenkov]

On Mon, Feb 14, 2011 at 12:22 AM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Thu, 10.02.11 07:02, Andrey Borzenkov (arvidjaar at gmail.com) wrote:
>
>> --- a/units/plymouth-start.service
>> +++ b/units/plymouth-start.service
>> @@ -12,7 +12,13 @@ Wants=systemd-ask-password-plymouth.path
>>  After=systemd-vconsole-setup.service udev-settle.service
>>  Before=systemd-ask-password-plymouth.service
>>
>> +# Dracut informs us with this flag file if plymouth is already running
>> +ConditionPathExists=!/dev/.systemd/plymouth
>> +
>>  [Service]
>>  ExecStart=/sbin/plymouthd --mode=boot
>>  ExecStartPost=-/bin/plymouth --show-splash
>>
> We added this flag file mostly to make it unnecessary to spawn plymouth
> twice.
>

Hmm ... how is systemd-ask-password-plymouth.service launched then?
Currently it pulled in by plymouth-start.service; but if
plymouth-start is skipped ...

Assuming we push patch to created flag file by plymouth (is patch
available anywhere BTW?); can systemd trigger unit startup when path
becomes available?