Control: reassign 757903 dh-systemd Control: forcemerge 751741 757903 Control: affects + 751741 syslog-ng-core
Gergely Nagy <alger...@balabit.hu> writes: > Turns out this is a known issue with systemd and socket activated > services (such as syslog-ng), see #736258 and #751744. However, we do > not use the recommended --restart-after-upgrade mechanism, and I'm > unsure whether that would fix the issue. I'm changing syslog-ng-core to use --restart-after-upgrade, but that will likely not solve the problem completely (although I have not been able to reproduce it locally), so I'm reassigning the bug to dh-systemd, and merging it with other similar issues. 3.5.6-2 will likely hit unstable by tonight, I would be very interested in hearing whether the problem persists with that version. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
