I've been contributing to this project for a long time, but stopped tracking BOINC status some time ago. Now that I've checked it, I see that almost all of my Milkyway tasks end with a segfault and 0 run time. I did start using grsec kernels about a year ago, and fear that Milkyway doesn't work on them. A typical crash looks like this in kernel log:

milkyway_nbody_[3985]: segfault at ffffffffffffffd0 ip 00000000004cfde3 sp 000003fe322f4818 error 7 in milkyway_nbody_1.62_x86_64-pc-linux-gnu__mt

but there are no other related entries from grsec or PaX. I'm pretty sure my hardware is fine and haven't seen this problem in other porjects.

Can anyone else confirm or verify whether Milkyway works on their system with a grsec kernel and PaX enabled? I don't want to stop contributing, but grsec is not optional for this system.

Thanks.

I've compiled the n-body application on my system as a dynamically-linked binary and just got a successful result with it.

It seems that the issue is not with grsec, but with one of the libraries statically linked into the official binary. Hope this helps someone else.

I would recommend compiling BOINC for your machine. I'm recently transitioning to an updated linux (Mageia1), and I note the precompiled binaries may not necessarily be compatible - eg: trying to run the BIONC (website) Ubuntu binary on a Fedora Core OS.

Also, reading the latest Fedora bugs for BOINC, seems it isn't happy with the latest releases as it breaks a few requirements for selinux - so I've noted trying to get this to run as a cron job will take more than simply adding it to cron bootup, but also looking at the selinux rules.

...for the moment, I'm starting it manually (but would prefer having it in cron).

---

http://www.joescat.com/boinc/