Control: severity -1 important Am 10.02.2017 um 17:49 schrieb Yuri D'Elia: > > With the update to 232-17, systemd-resolved fails to start with the > following error: >
> -- The error number returned by this process is 2. > Feb 10 17:46:31 test systemd[1]: systemd-resolved.service: Main process > exited, code=exited, status=226/NAMESPACE > Feb 10 17:46:31 test systemd[1]: Failed to start Network Name Resolution. > -- Subject: Unit systemd-resolved.service has failed This is caused by the addition of ReadWritePaths= in /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf I guess this should only be used in addition with ProtectSystem=, which is a recent upstream change but the Debian version does not use that yet. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
