Bug#837183: systemd: unprivileged call to systemd-resolve starts systemd-resolved even when masked
biebl at debian.org
Sat Sep 10 17:10:52 BST 2016
Am 10.09.2016 um 17:45 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/4122
> On 9 September 2016 at 19:36, Michael Biebl <biebl at debian.org> wrote:
>> Upstream's position on this is, that masks apply only on that particular
>> name and not for any existing aliases (symlinks)
> I interpret upstream's comment differently. They say "any alias
> pointed to it is masked", which (applied to this case) should mean
> that masking dbus-org.freedesktop.resolve1.service should not cause
> systemd-resolved.service to be masked.
Reading it again, I think you are correct with your interpretation.
I would expect the other way
> around to work though: all aliases *should* resolve to the same unit,
> and if that final unit is masked it should not be started.
Thanks for forwarding the issue.
Fwiw, I agree that it is very confusing if you can start a service via a
I remember a similar issue with the display-manager.service symlink.
Masking the actual service (gdm.service in my case), didn't actually
prevent gdm from being started.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers