On 5/5/20 7:41 PM, Andrei Borzenkov wrote:
a) Before= does not pull anything anywhere.
Yes I know sorry I did not use the correct term. I did not mean that.
b) as you already found, by default every service is ordered after
local-fs.target. You need DefalutDependencies=no if you want to
05.05.2020 18:15, Thomas HUMMEL пишет:
> On 4/28/20 5:36 PM, Thomas HUMMEL wrote:
>
>> 3) regarding local-fs dans remote-fs targets : I'm not really sure if
>> any fits in either passive or active units.
>
> Hello again,
>
> regarding local-fs.target : is it legit for a custom service unit to
>
On 5/5/20 5:27 PM, Thomas HUMMEL wrote:
On 5/5/20 5:15 PM, Thomas HUMMEL wrote:
-> this seems to be like an actual run and not only the queuing of a
job into the transaction which would be discarded afterwards when the
cycle is discovered ?
Ok I figure out this one : I was confusing the
On 5/5/20 5:15 PM, Thomas HUMMEL wrote:
-> this seems to be like an actual run and not only the queuing of a job
into the transaction which would be discarded afterwards when the cycle
is discovered ?
Ok I figure out this one : I was confusing the
systemd-tmpfiles-setup.service from initrd
On 4/28/20 5:36 PM, Thomas HUMMEL wrote:
3) regarding local-fs dans remote-fs targets : I'm not really sure if
any fits in either passive or active units.
Hello again,
regarding local-fs.target : is it legit for a custom service unit to
pull it in with a Before=local-fs.target (no Wants or
Hello,
Reading systemd.special(7) and using systemctl show -p
After,Before,Wants,Requires ..., I tried to figure out if my following
understanding is true:
doc says:
- an active target is when the consumer pulls in the dependency (ex:
network-online.target pulled in by nfs-mountd.service)
