software version
boinc_4.19_i686-pc-linux-gnu
-> setiathome_4.02_i686-pc-linux-gnu

$ uname -msr
Linux 2.4.26-om1 i686

I am running an openmosix cluster, and the boinc/setiathome will not migrate.

/proc/337# cat cantmove
monkey

monkey: the application is using files as shared memory

is there a patch / fix / howto / faq?
I have searched seti's site and boinc's site, and there isn't even a mention of openmosix, outside of the 'openmosix group'. (and the openmosix group makes no mention of actually running seti on an openmosix cluster)

---

i was also making an openmosix cluster, but didn't get as far as you. my master node doesn't have enough ram to run boinc (needs more than 64MB?!?) so i halted that project for the time being.

Boinc, unfortunately, uses shared memory segments to communicate between the worker applications and the core client... to share things like how far a workunit is and stuff like that.

Why they didn't use pipes is beyond me... but they didn't, so this is what we're stuck with.

For good reason, OpenMOSIX cannot migrate processes that use shared memory... it's hard to share shared memory between different nodes, unfortunately.

---

Rob

i was also making an openmosix cluster, but didn't get as far as you. my master node doesn't have enough ram to run boinc (needs more than 64MB?!?) so i halted that project for the time being.

Is there a good site for a noobe guide to boinc on openmosix/linux? sorry a bit off topic ;-)

---

i was also making an openmosix cluster, but didn't get as far as you. my master node doesn't have enough ram to run boinc (needs more than 64MB?!?) so i halted that project for the time being.

Is there a good site for a noobe guide to boinc on openmosix/linux? sorry a bit off topic ;-)

i used this:
http://www.gentoo.org/doc/en/openmosix-howto.xml
with gentoo linux for openmosix
but as Rob mentioned, BOINC does not benefit from its use