Michael Biebl wrote: > Am 25.12.2014 um 23:55 schrieb Jamie Heilman: > > Package: systemd > > Version: 215-8 > > Severity: normal > > > > Apparently systemd-localed depends on having namespace support in the > > kernel. It isn't immediately obvious to me why there is no graceful > > fallback approach. The manual page for systemd-localed doesn't call > > out this dependancy, and while I knew systemd-nspawn would have > > namespace requirements, this dependancy caught me by surprise: > > > > dbus[382]: [system] Activating via systemd: service > > name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' > > systemd[1]: Couldn't stat device /dev/pts/ptmx > > systemd[568]: Failed at step NETWORK spawning /lib/systemd/systemd-localed: > > Invalid argument > > systemd[1]: systemd-localed.service: main process exited, code=exited, > > status=225/NETWORK > > systemd[1]: Failed to start Locale Service. > > systemd[1]: Unit systemd-localed.service entered failed state. > > > > Unless there's some really good reason that systemd-localed shouldn't > > be usable on a system without namespaces, then I'm gonna say this is a > > bug. > > > > The reason afaics for requiring namespaces are the use of > > PrivateTmp=yes > PrivateDevices=yes > PrivateNetwork=yes > ProtectSystem=yes > > in /lib/systemd/system/systemd-localed.service
Ah yes, indeed if I toggle those off it appears to run ok. Default config that depends on features that are in the distro kernels isn't a bug, so this can be resolved. -- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
