[systemd-devel] Masking socket activated services is broken

[Michael Biebl]

2013/6/19 Michael Biebl <mbiebl at gmail.com>:
>
> To illustrate the problem: (non socket-activated service)

...

> In contrast to a socket-activated service (rsyslog)

...

> See the inconsistency?
> In case of rsyslog, I can also trigger the start, by starting
> syslog.socket again and running logger.

I've tried it with another socket activated service (avahi-daemon) and
could not reproduce the problem there.
So this might be specific to rsyslog / the sylsog integration.
Usually we have foo.service and a corresponding foo.socket.
With syslog, the rsyslog.service (or syslog-ng.service) use the
syslog.service Alias to map to syslog.socket
Maybe systemd get's confused because of this.

I've filed a bug now: https://bugs.freedesktop.org/show_bug.cgi?id=65946




--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?