Antw: [EXT] Re: Q: Difference between AssertPathExists and ConditionPathExists?

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Andrei Borzenkov <arvidjaar@xxxxxxxxx> schrieb am 17.03.2022 um 12:08 in
Nachricht
<CAA91j0VhohCGHpt1Lbk4Ro0PHXzMEOE6eVkTsoGf16rvJ4bWKg@xxxxxxxxxxxxxx>:
> On Thu, Mar 17, 2022 at 12:32 PM Ulrich Windl
> <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> Hi!
>>
>> When reading the manual page systemd.unit(5), I'm not quite sure what the 
> difference between AssertPathExists and ConditionPathExists is:
>>
>> (Condition)
>> If the specified absolute path name does not exist, the condition will fail.
>>
>> Vs.
>>
>> (Assert)
>> However, unlike the conditions settings, any assertion setting that is not 
> met results
>> in failure of the start job it was triggered by.
>> ----
>> What does that mean effectively?
>>
> 
> Assert makes the start job fail, which triggers any followup failure
> processing (like failure of other units Requiring this one). Condition
> silently skips starting of this unit but proceeds normally with
> starting dependent units.

OK, ist that "skip" actually a "skip once (and silently) for now", or is it more like a "delay until no longer true"?

Regards,
Ulrich