It's a known issue, the kernel people have been notified, and the general consensus is that breaking userspace this way is not bad, and the change is either going to be reverted, or reworked in such a way that maintains backwards compatibility.
It's pointless to try and work with the current -rc3 (and -rc4), as CAP_SYSLOG in its current form will not last. For the time being, disabling capability support is a reasonable workaround. In the future, once the reworked CAP_SYSLOG lands in Linus' tree, syslog-ng will be updated to support it. At the moment, however, the bug is on kernel-side, as it broke userspace. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
