Re: 2.6 Kernel Userspace Daemon 0.1-0602131225 (Hopefully attached)
"Matt Rechenburg" <matteverywhere-gM/[email protected]>
| Newsgroups | gmane.linux.cluster.openmosix.general |
|---|---|
| Message-ID | <[email protected]> |
(re-sending it since it gots rejected the first time) Hi Carl, Carl Radford (DC0854-IT) wrote: > Hi Matt, > > It should migrate. A couple of things to check, make sure you are running the "timewaster" that came with the source and not some other (the original) "timewaster" in your path, (it changes it's niceness, see TODO). Enable full debugging on the controller, with switches something like "-t3490 -u1334 -c -l255", make sure the other node is a drone "-t3490 -u1334 -d" (it wont migrate to another controller). The only reason why "timewaster" shouldn't migrate is if the controller & drone are deemed to > ah, ok, i guess i am still too much used to the "old" distributed openMosix loadbalancing for the 2.4 kernel. I now understood that there is one controller node and n drones. Will re-test this scenario soon. Still i am a bit worried about the kernel-panics i got during normal/manual migration .... maybe i will switched to the i386 architecture rpm or rebuild the kernel myself from the scratch. > be incompatible with each other. Create load on the controller, look for the "Compatibility" message, check to see if it considers the drone node to be incompatible (-1) with the controller. > will check. Many thanks for the hints, will keep you updated. stay tuned, Matt