Cascading oneshot units

[arvidjaar@xxxxxxxxx (Andrei Borzenkov)]

Ð?Ñ?пÑ?авлено Ñ? iPhone

> 20 маÑ?Ñ?а 2018 г., в 8:15, Andrei Borzenkov <arvidjaar at gmail.com> напиÑ?ал(а):
> 
> The simplest way is to add Wants=bar.service and After=bar.service to foo.service.

I mean of course Before=bar.service


> 
> Ð?Ñ?пÑ?авлено Ñ? iPhone
> 
>> 20 маÑ?Ñ?а 2018 г., в 7:44, Evan Klitzke <evan at eklitzke.org> напиÑ?ал(а):
>> 
>> I am wondering how to create a cascade of oneshot units that should run
>> on a timer. What I'm imagining is something like the following:
>> 
>> foo.timer
>> foo.service
>> bar.service
>> 
>> In this example foo.service and bar.service are both Type=oneshot with
>> no [Install] section. foo.timer declares Unit=foo.service, which causes
>> foo.service to run whenever the timer triggers. That's simple enough,
>> and I have that working.
>> 
>> I want bar.service to run after foo.service completes, as it operates on
>> some data generated by foo.service. I'm not sure what the magic bits are
>> to make this work. I could obviously work around the issue by wrapping
>> the logic for the two jobs in a shell script that runs the two actions
>> sequentially, but I rather like the logging and status utilities
>> provided by systemd, so having them as separate units seems preferable.
>> 
>> --
>> Evan Klitzke
>> https://eklitzke.org/
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel