On Fr, 06.09.24 14:49, Thomas Köller (tho...@koeller.dyndns.org) wrote:
> In 'man systemd.service', the description of ExecCondition= states:
>
> when an ExecCondition= command exits with exit code 1 through 254
> (inclusive), the remaining commands are skipped and the unit is not marked
> as fail
In 'man systemd.service', the description of ExecCondition= states:
when an ExecCondition= command exits with exit code 1 through 254
(inclusive), the remaining commands are skipped and the unit is not
marked as failed
What exactly does 'the remaining commands' mean? Other commands from
sub
В Fri, 10 Oct 2014 10:14:47 -0700
PGNd пишет:
> systemd v214 introduced the new network-related target, "network-pre.target".
>
> It cleanly provides a convenient and timley pre-network state trigger for
> Before= use in unit ordering.
>
> As originally conceived, and currently implemented, it
On Fri, Oct 10, 2014 at 7:14 PM, PGNd wrote:
> (2) [systemd-networkd] does not appear to be required for either
> network.target, or network-online.target ...
Correct.
The point of network-pre.target is that whatever network manager you
are using must be ordered After= it, so that your firewall
systemd v214 introduced the new network-related target, "network-pre.target".
It cleanly provides a convenient and timley pre-network state trigger for
Before= use in unit ordering.
As originally conceived, and currently implemented, it's of particular use for
secure, early init of firewalls,
