Skip to contentSkip to conversation

OE installs /sbin/nologin, but systemd accounts use /bin/nologin

DISCUSSION Robert P. J. Day 1 participant 1 message Apr 23, 2020

lore
Share & tools
lore
#0 lore raw

followup to previous post ... with master oe-core, i did:

* MACHINE = qemuarm64
* core-image-minimal

with only customization:

INIT_MANAGER = "systemd"

the end result was a bootable QEMU image which had the executable /sbin/nologin, but a number of systemd-related user accounts with login shell "/bin/nologin" (which does not exist in the image).

the systemd accounts are clearly created as a result of this from
the systemd recipe file (which hardcodes the selection of /bin/nologin):

USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'networkd', '--system -d / -M --shell /bin/nologin systemd-network;', '', d)}"

USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'resolved', '--system -d / -M --shell /bin/nologin systemd-resolve;', '', d)}"

USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'timesyncd', '--system -d / -M --shell /bin/nologin systemd-timesync;', '', d)}"

is this a bug? how does one properly make this consistent?

rday