On Thu, Apr 2, 2009 at 09:29, Alex Efros <[email protected]> wrote: > Hi! > > switching off CONFIG_PAX_MPROTECT solve this issue > > Now I'll try to paxctl -m for /bin/bash and /sbin/runit-init (with > switched on CONFIG_PAX_MPROTECT, of course)... yeah, that solves this > issue too. > > > So, now we've very strange situation: PaX require -m for process N1. > This isn't related to my init (runit-init) because same happens for bash. > This happens only on one server - several other servers with exactly same > hardware, kernel and gentoo configuration doesn't have this issue.
I question whether your configurations are *precisely* the same. If I had to guess (and I do), I'd guess that the system in question wasn't wholly built with the -hardened toolchain. Once you grow beyond a few identical systems, it often becomes beneficial to use a single central build system and PORTAGE_BINHOST with 'emerge -gK' to install the other systems.
