tags 636501 + fixed-upstream
quit
Gergely Nagy wrote:
> That is correct, even though I personally find the warning stupid and
> only annoying users.
Fixed by v3.1-rc2~33 (cap_syslog: don't use WARN_ONCE for
CAP_SYS_ADMIN deprecation warning). Thanks for your help.
--
To UNSUBSCRIBE, email t
tags 636501 = upstream
forwarded 636501
http://thread.gmane.org/gmane.linux.kernel/1098435/focus=1174954
quit
Gergely Nagy wrote:
> I like the printk_once() a lot better, indeed. Would be awesome to have
> it upstream too..
Thanks for the encouragement. Further discussion should happen
upstrea
Jonathan Nieder writes:
> Gergely Nagy wrote:
>> Jonathan Nieder writes:
>
>>> 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.
>
> I agree, especia
Gergely Nagy wrote:
> Jonathan Nieder writes:
>> 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.
I agree, especially since it's a normal condition when
Jonathan Nieder 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 in
Hi,
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 sy
6 matches
Mail list logo
