Bug#636501: WARNING: at kernel/printk.c:293 do_syslog+0x74/0x38f()

[Gergely Nagy <algernon@madhouse-project.org>]

Jonathan Nieder <jrnieder@gmail.com> writes:

> maximilian attems wrote:
>> On Wed, Aug 03, 2011 at 04:10:04PM +0200, Ralf Hildebrandt wrote:
>
>>> After/deuring the installation of syslog-ng I found the attached trace
>>> in dmesg!
>>
>> oho, is that reproducible on 3.0 that you find in unstable?
>
> It looks like intended behavior.  I guess the syslogd should be using
> CAP_SYSLOG these days.

That is correct, even though I personally find the warning stupid and
only annoying users. It is harmless though, and future versions of
syslog-ng will use CAP_SYSLOG on systems where it is available.

Personally, I'd reassign this bug to syslog-ng, and merge it with the
already existing similar report. (Could also use an upstream and a
pending tag, as the issue is fixed in both the 3.2 and 3.3 branches
upstream, and will be part of the next upstream release)

-- 
|8]