Make systemd as default init manager and configure wired network
v3 cover Make systemd as default init manager and configure wired network
From: Kai Kang <[email protected]>
v3:
* add the patch to make systemd as default init manager
* rename the .network with wired.network
* call to bb.utils.contains('OVERRIDES', ...) is not right. Install wired.network unconditionally and remove in in do_install_append_qemuall() BTW, bb.utils.contains('IMAGE_CLASSES', 'qemuboot', ...) from layer meta-yoe doesn't work for genericx86 that why I didn't use it.
Testededed on genericx86-64.
Run testimage with qemux86-64:
MACHINE ?= "qemux86-64"
IMAGE_CLASSES += "testimage"
QEMU_USE_SLIRP = "1"
TEST_SERVER_IP = "xxx"
$ bitbake core-image-sato -c testimage SUMMARY: core-image-sato () - Ran 60 tests in 1042.949s core-image-sato - OK - All required tests passed (successes=42, skipped=18, failures=0, errors=0) NOTE: Tasks Summary: Attempted 723 tasks of which 722 didn't need to be rerun and all succeeded.
Kai Kang (2):
local.conf.sample: make systemd as default init manager
systemd-conf: configure wired network with dhcp
meta-poky/conf/local.conf.sample | 9 +++++++++ meta-poky/conf/local.conf.sample.extended | 9 --------- meta/recipes-core/systemd/systemd-conf/wired.network | 9 +++++++++ meta/recipes-core/systemd/systemd-conf_242.bb | 6 ++++++ 4 files changed, 24 insertions(+), 9 deletions(-) create mode 100644 meta/recipes-core/systemd/systemd-conf/wired.network
--
2.18.0
PATCH v3 1/2 local.conf.sample: make systemd as default init manager
From: Kai Kang <[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
[YOCTO #13031]
--- meta-poky/conf/local.conf.sample | 9 +++++++++ meta-poky/conf/local.conf.sample.extended | 9 --------- 2 files changed, 9 insertions(+), 9 deletions(-)
meta-poky/conf/local.conf.sample +9 -0
@@ -249,3 +249,12 @@ PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" # track the version of this file when it was generated. This can safely be ignored if # this doesn't mean anything to you. CONF_VERSION = "1" + +# +# Use systemd for system initialization +# +DISTRO_FEATURES_append = " systemd" +DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" +VIRTUAL-RUNTIME_login_manager = "shadow-base" +VIRTUAL-RUNTIME_init_manager = "systemd" +VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
meta-poky/conf/local.conf.sample.extended +0 -9
@@ -377,12 +377,3 @@ DISTRO_FEATURES_remove = "x11" #VIRTUAL-RUNTIME_initscripts = "initscripts" #VIRTUAL-RUNTIME_keymaps = "keymaps" #DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" - -# -# Use systemd for system initialization -# -#DISTRO_FEATURES_append = " systemd" -#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" -#VIRTUAL-RUNTIME_login_manager = "shadow-base" -#VIRTUAL-RUNTIME_init_manager = "systemd" -#VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
Signature · 1 line
2.18.0
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 10 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of [email protected]
Sent: den 23 maj 2019 10:26
To: [email protected]
Cc: [email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 4 lines
From: Kai Kang <[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
Quoted 54 lines
[YOCTO #13031]
Signed-off-by Kai Kang <[email protected]>--- meta-poky/conf/local.conf.sample | 9 +++++++++ meta-poky/conf/local.conf.sample.extended | 9 --------- 2 files changed, 9 insertions(+), 9 deletions(-)meta- renamed from meta-poky/conf/local.conf.sample +0
-0poky/conf/local.conf.sample
index9068e567dc..3a07105e44100644meta-poky/conf/local.conf.sample +0
-0@@ -249,3 +249,12 @@ PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" # track the version of this file when it was generated. This cansafely be ignored if
# this doesn't mean anything to you. CONF_VERSION = "1"meta-poky/conf/local.conf.sample +9
-0+ +# +# Use systemd for system initialization +# +DISTRO_FEATURES_append = " systemd" +DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" +VIRTUAL-RUNTIME_login_manager = "shadow-base" +VIRTUAL-RUNTIME_init_manager = "systemd" +VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"meta- renamed from meta-poky/conf/local.conf.sample.extended +0
-0poky/conf/local.conf.sample.extended
index26603debe6..e20fc5dbf3100644meta-poky/conf/local.conf.sample.extended +0
-10@@ -377,12 +377,3 @@ DISTRO_FEATURES_remove = "x11" #VIRTUAL-RUNTIME_initscripts = "initscripts" #VIRTUAL-RUNTIME_keymaps = "keymaps" #DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" - -# -# Use systemd for system initialization -# -#DISTRO_FEATURES_append = " systemd" -#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" -#VIRTUAL-RUNTIME_login_manager = "shadow-base" -#VIRTUAL-RUNTIME_init_manager = "systemd" -#VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" --2.18.0
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 12 lines · Peter Kjellerstedt
Quoted 12 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of [email protected]
Sent: den 23 maj 2019 10:26
To: [email protected]
Cc: [email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerFrom: Kai Kang <[email protected]>
Quoted 8 lines
Quoted 2 lines
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Quoted 62 lines
Quoted 51 lines
[YOCTO #13031]
Signed-off-by Kai Kang <[email protected]>--- meta-poky/conf/local.conf.sample | 9 +++++++++ meta-poky/conf/local.conf.sample.extended | 9 --------- 2 files changed, 9 insertions(+), 9 deletions(-)meta- renamed from meta-poky/conf/local.conf.sample +0
-0poky/conf/local.conf.sample
index9068e567dc..3a07105e44100644meta-poky/conf/local.conf.sample +0
-0@@ -249,3 +249,12 @@ PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" # track the version of this file when it was generated. This cansafely be ignored if
# this doesn't mean anything to you. CONF_VERSION = "1"meta-poky/conf/local.conf.sample +9
-0+ +# +# Use systemd for system initialization +# +DISTRO_FEATURES_append = " systemd" +DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" +VIRTUAL-RUNTIME_login_manager = "shadow-base" +VIRTUAL-RUNTIME_init_manager = "systemd" +VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"meta- renamed from meta-poky/conf/local.conf.sample.extended +0
-0poky/conf/local.conf.sample.extended
index26603debe6..e20fc5dbf3100644meta-poky/conf/local.conf.sample.extended +0
-10@@ -377,12 +377,3 @@ DISTRO_FEATURES_remove = "x11" #VIRTUAL-RUNTIME_initscripts = "initscripts" #VIRTUAL-RUNTIME_keymaps = "keymaps" #DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" - -# -# Use systemd for system initialization -# -#DISTRO_FEATURES_append = " systemd" -#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" -#VIRTUAL-RUNTIME_login_manager = "shadow-base" -#VIRTUAL-RUNTIME_init_manager = "systemd" -#VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" --2.18.0
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 23 lines
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 10 lines · Peter Kjellerstedt
-----Original Message-----
From: mailto:[email protected] <openembedded- mailto:[email protected]> On Behalf Of mailto:[email protected]
Sent: den 23 maj 2019 10:26
To: mailto:[email protected]
Cc: mailto:[email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 4 lines
From: Kai Kang <mailto:[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
Quoted 8 lines
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and http://packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Ok, then I'd say the change belongs in poky.conf. Doing this kind of changes in local.conf.sample seems very wrong to me. Why? Because if I have an existing build tree it will not be affected, but if I setup a new tree with oe-init-build-env it will all of a sudden behave differently from the old tree. In my mind, local.conf.sample should only be used for things the user are likely to want to configure to adapt the build for his/her environment, not to define the distribution (that's what poky.conf is for).
//Peter
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 33 lines · Peter Kjellerstedt
Quoted 24 lines
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 10 lines · Peter Kjellerstedt
-----Original Message-----
From: mailto:[email protected] <openembedded- mailto:[email protected]> On Behalf Of mailto:[email protected]
Sent: den 23 maj 2019 10:26
To: mailto:[email protected]
Cc: mailto:[email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 4 lines
From: Kai Kang <mailto:[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
Quoted 8 lines
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and http://packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Quoted 7 lines
Ok, then I'd say the change belongs in poky.conf. Doing this kind of changes in local.conf.sample seems very wrong to me. Why? Because if I have an existing build tree it will not be affected, but if I setup a new tree with oe-init-build-env it will all of a sudden behave differently from the old tree. In my mind, local.conf.sample should only be used for things the user are likely to want to configure to adapt the build for his/her environment, not to define the distribution (that's what poky.conf is for).
yes distro config is right place.
Quoted 3 lines
//Peter
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
In reply to Peter KjellerstedtQuoted 30 lines · Peter Kjellerstedt
Quoted 22 lines
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 10 lines · Peter Kjellerstedt
-----Original Message-----
From: mailto:[email protected] <openembedded- mailto:[email protected]> On Behalf Of mailto:[email protected]
Sent: den 23 maj 2019 10:26
To: mailto:[email protected]
Cc: mailto:[email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 4 lines
From: Kai Kang <mailto:[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
Quoted 8 lines
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and http://packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Quoted 7 lines
Ok, then I'd say the change belongs in poky.conf. Doing this kind of changes in local.conf.sample seems very wrong to me. Why? Because if I have an existing build tree it will not be affected, but if I setup a new tree with oe-init-build-env it will all of a sudden behave differently from the old tree. In my mind, local.conf.sample should only be used for things the user are likely to want to configure to adapt the build for his/her environment, not to define the distribution (that's what poky.conf is for).
If put the settings to poky.conf, it is complicated to override the settings and hard for users to turn back to sysvinit when he/she wants. And every time updates local.conf.sample which is not just update comments, the old build and new build are differently, such as
commit 18bead102afabffcf3842ee099dcd22b8a598b8d
Author: Alexander Kanavin <[email protected]> Date: Wed Feb 27 18:47:33 2019 +0100
local.conf.sample: adjust the qemu configuration to refer to qemu-system-native
(From meta-yocto rev: aa16ed1b2c0f358d244a50a41be19d80935d3cc8)
meta-poky/conf/local.conf.sample +0 -0
@@ -241,7 +241,7 @@ BB_DISKMON_DIRS ??= "\
# seen. The two lines below enable the SDL backend too. By default libsdl2-native will # be built, if you want to use your host's libSDL instead of the minimal libsdl built # by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" +PACKAGECONFIG_append_pn-qemu-system-native = " sdl" PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" #ASSUME_PROVIDED += "libsdl2-native"
and more earlier:
commit 63dcfa8f1394475073f6dbb5f3f6ede284d5a305
Author: Mark Hatle <[email protected]>
Date: Mon Aug 15 16:29:34 2016 -0500
Revert "local.conf.sample: Disable prelink by default"
This reverts commit 300f858ba07c938427ccd05a3d7220027a03d461.
Reenable prelink
(From meta-yocto rev: 91705d8ae9f56d1de4f0fdcd6a9654b75921aa8c)
meta-poky/conf/local.conf.sample +0 -0
@@ -152,8 +152,7 @@ EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
# - 'image-swab' to perform host system intrusion detection
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -# image-prelink disabled for now due to issues with IFUNC symbol relocation -USER_CLASSES ?= "buildstats image-mklibs"
+USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#
# Runtime testing of images
Regards,
Kai
Quoted 3 lines
//Peter
Signature · 1 line
Kai Kang
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 40 lines · Kang Kai
Quoted 30 lines · Peter Kjellerstedt
Quoted 22 lines
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 10 lines · Peter Kjellerstedt
-----Original Message-----
From: mailto:[email protected] <openembedded- mailto:[email protected]> On Behalf Of mailto:[email protected]
Sent: den 23 maj 2019 10:26
To: mailto:[email protected]
Cc: mailto:[email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 4 lines
From: Kai Kang <mailto:[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
Quoted 8 lines
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and http://packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Quoted 7 lines
Ok, then I'd say the change belongs in poky.conf. Doing this kind of changes in local.conf.sample seems very wrong to me. Why? Because if I have an existing build tree it will not be affected, but if I setup a new tree with oe-init-build-env it will all of a sudden behave differently from the old tree. In my mind, local.conf.sample should only be used for things the user are likely to want to configure to adapt the build for his/her environment, not to define the distribution (that's what poky.conf is for).
Quoted 1 line
If put the settings to poky.conf, it is complicated to override the settings and hard for users to turn back to sysvinit when he/she wants.
If you want to make this override-able you could do something like this (forgive any mistakes or bad wrapping I'm just writing this in my email client without testing):
POKY_USE_SYSTEMD ?= "1"DISTRO_FEATURES_append = "${@bb.utils.conditional("POKY_USE_SYSTEMD", "1", "systemd", "", d)}" ... etc ...
That would allow someone to set POKY_USE_SYSTEMD = "0" in their local.conf.
There may be more elegant ways to do this as well, but we the default can certainly be set in the distro config in a way that can be overridden in local.conf.
Thanks,
Signature · 3 lines
Paul Barker Managing Director & Principal Engineer Beta Five Ltd
Re: [PATCH v3 1/2] local.conf.sample: make systemd as default init manager
Quoted 47 lines · Paul Barker
Quoted 40 lines · Kang Kai
Quoted 30 lines · Peter Kjellerstedt
Quoted 22 lines
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: den 23 maj 2019 22:59
To: Peter Kjellerstedt <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 10 lines · Peter Kjellerstedt
-----Original Message-----
From: mailto:[email protected] <openembedded- mailto:[email protected]> On Behalf Of mailto:[email protected]
Sent: den 23 maj 2019 10:26
To: mailto:[email protected]
Cc: mailto:[email protected]
Subject: [OE-core] [PATCH v3 1/2] local.conf.sample: make systemd as default init managerQuoted 4 lines
From: Kai Kang <mailto:[email protected]>
Move configurations from local.conf.sample.extended to local.conf.sample to make systemd as default init manager for poky.
Quoted 8 lines
If we're going to change the default init manager to be systemd, wouldn't it be more appropriate to change the real default values in bitbake.conf and http://packagegroup-core-boot.bb? And then include an example in local.conf.sample.extended to show how to configure sysvinit as init manager?
That would change it for Oe-core and other distributions as well which is not the intention
Quoted 7 lines
Ok, then I'd say the change belongs in poky.conf. Doing this kind of changes in local.conf.sample seems very wrong to me. Why? Because if I have an existing build tree it will not be affected, but if I setup a new tree with oe-init-build-env it will all of a sudden behave differently from the old tree. In my mind, local.conf.sample should only be used for things the user are likely to want to configure to adapt the build for his/her environment, not to define the distribution (that's what poky.conf is for).
Quoted 1 line
If put the settings to poky.conf, it is complicated to override the settings and hard for users to turn back to sysvinit when he/she wants.
If you want to make this override-able you could do something like this (forgive any mistakes or bad wrapping I'm just writing this in my email client without testing):
Quoted 7 lines
POKY_USE_SYSTEMD?= "1"DISTRO_FEATURES_append= "${@bb.utils.conditional("POKY_USE_SYSTEMD", "1", "systemd", "", d)}" ... etc ...That would allow someone to set
POKY_USE_SYSTEMD = "0"in their local.conf.There may be more elegant ways to do this as well, but we the default can certainly be set in the distro config in a way that can be overridden in local.conf.
OK. I'll move them to poky.conf.
Thanks.
Kai
Quoted 3 lines
Thanks,
Signature · 1 line
Kai Kang
PATCH v3 2/2 systemd-conf: configure wired network with dhcp
In reply to [email protected]From: Kai Kang <[email protected]>
Add a configure file for systemd.networkd to configure wired network interfaces with dhcp. It works with common network interfaces such eth0 and eno1. And do not install it for qemu bsps.
Refer to
https://github.com/YoeDistro/meta-yoe/tree/master/recipes-core/systemd
[YOCTO #13057]
--- meta/recipes-core/systemd/systemd-conf/wired.network | 9 +++++++++ meta/recipes-core/systemd/systemd-conf_242.bb | 6 ++++++ 2 files changed, 15 insertions(+) create mode 100644 meta/recipes-core/systemd/systemd-conf/wired.network
meta/recipes-core/systemd/systemd-conf/wired.network new file +9 -0
@@ -0,0 +1,9 @@ +[Match] +Name=en* eth* + +[Network] +DHCP=yes + +[DHCP] +RouteMetric=10 +ClientIdentifier=mac
meta/recipes-core/systemd/systemd-conf_242.bb +6 -0
@@ -10,17 +10,22 @@ SRC_URI = "\ file://logind.conf \ file://system.conf \ file://system.conf-qemuall \ + file://wired.network \ " do_install() { install -D -m0644 ${WORKDIR}/journald.conf ${D}${systemd_unitdir}/journald.conf.d/00-${PN}.conf install -D -m0644 ${WORKDIR}/logind.conf ${D}${systemd_unitdir}/logind.conf.d/00-${PN}.conf install -D -m0644 ${WORKDIR}/system.conf ${D}${systemd_unitdir}/system.conf.d/00-${PN}.conf + install -D -m0644 ${WORKDIR}/wired.network ${D}${systemd_unitdir}/network/80-wired.network } # Based on change from YP bug 8141, OE commit 5196d7bacaef1076c361adaa2867be31759c1b52 do_install_append_qemuall() { install -D -m0644 ${WORKDIR}/system.conf-qemuall ${D}${systemd_unitdir}/system.conf.d/01-${PN}.conf + + # Do not install wired.network for qemu bsps + rm -rf ${D}${systemd_unitdir}/network } PACKAGE_ARCH = "${MACHINE_ARCH}"
@@ -29,4 +34,5 @@ FILES_${PN} = "\ ${systemd_unitdir}/journald.conf.d/ \ ${systemd_unitdir}/logind.conf.d/ \ ${systemd_unitdir}/system.conf.d/ \ + ${systemd_unitdir}/network/ \ "
Signature · 1 line
2.18.0