Indeed! While it will take some time, I can highly recommend reading the entirety of the various man pages: systemd.unit, systemd.service, systemd.target, systemd.special. I've been able to take advantage of many 'not obvious' features by doing that. On Mon, Jan 24, 2022 at 7:21 AM Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote: > > On 24/01/2022 11:08, Kevin P. Fleming wrote: > > According to 'man systemd.unit' it goes in the '[Unit]' section, like > > all other dependency statements. > > Thank you very much. The usual problem of "where's the docu I'm looking > for?" :-) > > Cheers, > Wol > > > > On Sun, Jan 23, 2022 at 3:15 PM Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote: > >> > >> On 23/01/2022 19:44, Andrei Borzenkov wrote: > >>> Where dependency to /home comes from? It is not in your unit file. > >> > >> If it thinks my unit depends on /home, that's wrong. /home comes from > >> fstab, and the partition is not available until AFTER my service has > >> run. Home is on an lv, which is on raid, which is on dm-integrity, which > >> isn't available until my service has turned it on ... > >>> > >>> Otherwise normal services are ordered by default after sysinit.target and > >>> local file systems are ordered before sysinit.target so you have loop. Add > >>> DefaultDependencies=no to your service definition. > >> > >> Thanks. I presume that goes in the [Install] section? I can find plenty > >> of stuff telling me WHAT DefaultDependencies is, but nothing I can > >> understand that tells me WHERE it goes. > >> > >> Thanks, > >> Cheers, > >> Wol >