Am 01.12.23 um 16:19 schrieb Matt Zagrabelny:
On Fri, Dec 1, 2023 at 9:16 AM Reindl Harald <h.reindl@xxxxxxxxxxxxx
<mailto:h.reindl@xxxxxxxxxxxxx>> wrote:
Am 01.12.23 um 15:12 schrieb Serg:
> On 12/1/23 14:04, Reindl Harald wrote:
>> keep your dirty fingers from files which are part of a package
while
>> the package manager keeps it's dirty fingers from /etc
>
> When systemctl edit nftables.service is used it does not modify
original
> file, instead it creates override configuration.
but you *can not* remove "Before=network-pre.target" with a drop-in,
you
can only add additional "Before" conditions
I believe you can clear various attributes:
Before=
Before=foo
That will set Before to be only "foo"
that could be interesting in case there are more than one drop-ins which
is very common - i use systemd-units and driop-ins from day one excessive
anyways, 9 out of 10 people don't know what they are doing when they
deal with systemd configs and wonder what happens after random updates
because they touch stuff in /usr, don't know about drop-ins, don't know
about overrides and don't understand the conecpt of system versus local
configs
otherwise that thread won't exist:
* upstream mailing list for a distribution-unit
* asking why common sense is default
* asking if it's fine to edit it
that would lead in touching /lib/systemd/system/nftables.service and
last only until the next update
----------------
What is the reason to start nftable service before networkd configured
by default? Is this the intended behavior for nftable? Or is it fine to
modify the service unit file and change the dependency to fit different
use cases?
