L-o-n-g delay for rc.local in systemd on Ubuntu.

[Ralf Mardorf]

On Tue, 08 Aug 2017 18:53:03 +0200, Xen wrote:
>Ralf Mardorf schreef op 08-08-2017 17:02:
>> Why don't you let a systemd unit start your extreme lightweight stuff
>> instead of rc.local?  
>
>Maybe because he didn't know how to do that.
>
>Hint: it is more useful to give people a hint, than to ask why they
>are not using that hint

So actually even you point out, that I gave a hint, while at the same
time you reply without providing any useful information at all.

Since the OP doesn't provide much information, there's nothing more I
could provide. We only know that the OP's init system is systemd and
that the OP is using something that does belong to a different init
system. the OP does know that systemd replaced another init system. The
OP places value on extreme lightweight stuff during the boot process and
seemingly is able to estimate what is or isn't lightweight. It should
be clear that if an init system allows to use something from another
init system, this is an additional layer, perhaps a lightweight layer,
but you wouldn't call any layer extreme lightweight. IOW to start
extreme lightweight stuff, it could be useful to use the init's systems
mechanisms to start it, to keep everything as lightweight as possible.
We could assume that somebody aware of the init system, able to start
something customized at boot time, should have investigated some time to
get this knowledge and likely decided knowingly against systemd units.
However, even if the OP never should have heard about systemd units, the
question still is a pointer into the right direction. IOW it doesn't
matter if the hint is provided by a question or by another sentence
structure, the answer hint remains the same.

The OP should consider to google for "systemd unit". How to use the
systemd unit or units depends on when and what shuld be started during
startup.