Bug#724796: [Pkg-systemd-maintainers] Bug#724796: systemd loses track of rsyslog state when syslog.service is replaced during upgrade
Michael Biebl
biebl at debian.org
Sat Jun 28 15:38:03 BST 2014
Am 27.11.2013 11:27, schrieb Alessandro Ghedini:
>> To reproduce the issue, one can follow those steps:
>> - Make sure rsyslog is installed and running.
>> status: step1.txt
>> - rm -f /etc/systemd/system/syslog.service
>> - systemctl daemon-reload
>> status: step2.txt
>> - re-create symlink: systemctl enable rsyslog.service
>
> Another solution that seems to work is running "systemctl reenable ..." instead
> of just "enable". rsyslog does not get killed and correctly appears as
> "active (running)" afterwards and can be restarted manually without problems.
I tried systemctl reenable instead of enable, as you suggested. Didn't
help. The error was the same.
As soon as the symlink is removed by dpkg (was previously shipped in the
package) and a daemon-reload is triggered, systemd loses the state.
--
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://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140628/a26d6f38/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list