On 28/05/2019 07.38, Andrei Borzenkov wrote:
26.05.2019 15:35, Hans-Peter Jansen пишет:
Thanks, Andrei, for your response.
Given, that VMs tend to create a *lot* of load, which would better delayed after regular boot services, doesn't boot-complete.target fit that bill?
I do not know what boot-complete.target is. You may consider adding timer with OnStartupSec that starts your service; OnStartup comes as close to "after everything else" as can be expected given systemd architecture.
* The boot-complete.target target unit (see systemd.special(7)) serves as a generic extension point both for units that shall be considered necessary to consider a boot successful on one side (example: systemd-boot-check-no-failures.service as described above), and units that want to act only if the boot is successful on the other (example: systemd-bless-boot.service as described above). https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT.html Does not appear to exist on Leap; maybe on factory. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)