job migration

[Daniel Ridge]

On Fri, 9 Mar 2001, Cosmik Debris wrote:

> I don't think you can do process migration with scripts. For process
> migration one has to be able to "pick up" a running job and move it along
> with it's open file handles etc. Not an easy task.

Funny you should mention this....

We've got a little library we use internally. It's an LD_PRELOAD for
bash that uses it's library constructor to set up a signal handler on
SIGPWR. If you put the node you want to go to in the environment and
send yourself SIGPWR, the current process moves to that node.

This was done just for bash so that I could create bash bindings for
bproc. :)

I now have shell scripts that just wander around the cluster like worms
doing various things. The even sicker part is that we wrapper execve()
to do bproc_move()/bproc_execmove() so that bash can run subprograms even
though none are installed locally.

Regards,
	Dan Ridge
	Scyld Computing Corporation