mån 2009-04-20 klockan 21:13 +0200 skrev pagee...@freemail.hu: > On 20 Apr 2009 at 21:03, Peter Hjalmarsson wrote: > > > I realised earlier today that foldingathome (installed with the help of > > portage) had not started a new WU since 5 of april, and when I started > > to investigate I found out that the "cores" had problem running. > > > > cd /opt/foldingathome && > > paxctl -c FahCore_*.exe && > > paxctl -PEMrXS FahCore_*.exe > > > > makes it work again. > > foldingathome has worked in the past without problems, and I do not > > really know what have changed more then some kernel-upgrades (but > > booting the last kept 2.6.27-hardened did not help either) and keeping > > the userland up to stable x86. > > What can I do to not have to do this dance? > > can you re-enable pax on the binaries and see if they produce any logs > (pax kills)? if they do, try to remove mprotect only and see if that > helps. the other issue could be a bad glibc and lack of GNU_STACK headers, > execstack -c would fix that without having to compromise on pax. > > >
I find nothing in ay logs from pax what ever I try, the reason I tried with PAX-permissions was a hounch. Only disable mprotect does not change anything. I cannot find execstack on the system, what package provides that file?
