[systemd-devel] Masking socket activated services is broken
Kok, Auke-jan H
auke-jan.h.kok at intel.com
Wed Jun 19 09:36:49 PDT 2013
On Tue, Jun 18, 2013 at 10:15 PM, Michael Biebl <mbiebl at gmail.com> wrote:
> Hi,
>
> I've run "systemctl mask rsyslog.service", but the service can still
> be started via
> "systemctl start rsyslog.service" or by generating a log message.
>
> Looks like a bug to me.
Why would it be? Masking just removes the unit from the dependency
tree of a target - I kinda prefer being able to mask and manually
start a unit. The alternative, which is what you suggest, is that the
administrator is prohibited from starting a unit - sounds much worse
to me.
Cheers,
Auke
More information about the systemd-devel
mailing list