[systemd-devel] Masking socket activated services is broken

Andrey Borzenkov arvidjaar at gmail.com
Wed Jun 19 10:43:05 PDT 2013


В Wed, 19 Jun 2013 09:36:49 -0700
"Kok, Auke-jan H" <auke-jan.h.kok at intel.com> пишет:

> 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.

masked unit does not exist. Its content is /dev/null, so there is
nothing to start. It is just placeholder.

I'm not sure whether it is still possible to start unit using full name
but it definitely should not be possible to start unit using unit name,
by any means.


More information about the systemd-devel mailing list