* OE installs /sbin/nologin, but systemd accounts use /bin/nologin
@ 2020-04-23 21:44 Robert P. J. Day
0 siblings, 0 replies; only message in thread
From: Robert P. J. Day @ 2020-04-23 21:44 UTC (permalink / raw
To: OE Core mailing list
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-23 21:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-23 21:44 OE installs /sbin/nologin, but systemd accounts use /bin/nologin Robert P. J. Day
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.