| 1 |
On 30 Oct 2007 at 18:18, Brian Kroth wrote: |
| 2 |
|
| 3 |
> It also seems strange to me that only nagios and cactid would crap out |
| 4 |
> on this. If I run the cacti poller just through php I get no errors. |
| 5 |
> The server also hosts ntp, portage over NFS, syslog-ng, mysql, dovecot, |
| 6 |
> sec, postfix, and a bunch of management scripts for other servers. It's |
| 7 |
> a busy thing, so if bad ram were the case, I'd expect to see them in |
| 8 |
> other places. Possibly just bad code on cactid/nagios' part? Should |
| 9 |
> PAX complain then? |
| 10 |
|
| 11 |
PaX only logs bad behaviour when it's about unintended code execution, |
| 12 |
this bug here is a kernel-internal consistency check, it doesn't mean |
| 13 |
that the triggering userland app has a bug, it may very well just manage |
| 14 |
to trigger a kernel bug (which in turn could be in PaX for all i know). |
| 15 |
it'd be nice if you could find a way to reproduce it, also if you could |
| 16 |
test with 2.6.23-pax. |
| 17 |
|
| 18 |
> Also including emerge --info for anyone who's interested. Should I be |
| 19 |
> opening a bug for this? |
| 20 |
> |
| 21 |
> # pcregrep " page:" /var/log/kern.log | sed 's/.*\(page:\S\+\).*/\1/' | |
| 22 |
> perl -e 'while (<>) { $data{$_}++ }; for (keys %data) { print $data{$_} |
| 23 |
> . " " . $_ ; };' |
| 24 |
> |
| 25 |
> 1 page:c14320e0 |
| 26 |
|
| 27 |
what is more interesting is the other fields, especially flags. |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-hardened@g.o mailing list |
Archives