[Pkg-systemd-maintainers] Bug#731742: Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start
Michael Biebl
biebl at debian.org
Wed Mar 5 22:49:33 GMT 2014
Am 04.03.2014 03:10, schrieb Eric Cooper:
> On Mon, Mar 03, 2014 at 11:55:18PM +0100, Michael Biebl wrote:
>> > If you can reproduce the issue reliably, can you send us the output of
>> > systemctl status rsyslog.service syslog.socket
>> > and journalctl -b
> Yes, it happens every time I boot:
>
> $ sudo systemctl status rsyslog.service syslog.socket
> rsyslog.service - System Logging Service
> Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
So, I might have been confused by that output, where rsyslog.service is
mentioned as "enabled".
If I remove
/etc/systemd/system/multi-user.target.wants/rsyslog.service,
systemd still considers the service to be enabled.
Only if I remove *both*
/etc/systemd/system/multi-user.target.wants/rsyslog.service and
/etc/systemd/system/syslog.service,
the service is listed as disabled.
I think this arguably a bug. Only if everything as specified under
[Install] is setup, I would consider a service to be (fully) enabled.
Michael, Tollef, your thoughts?
--
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...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140305/400184fd/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list