douglis@MINT.BERKELEY.EDU (Fred Douglis) (08/12/89)
I tried a new version of inews that may or may not have actually worked. I don't see the article on the host I sent it to, so I'm worried it got dropped on the floor. Please forgive me if this is a duplicate. ================================================================ Newsgroups: comp.os.misc From: douglis@kvetching.Berkeley.EDU (Fred Douglis) Subject: Re: Process migration on UNIX, anyone?? References: <12402@s.ms.uky.edu> Reply-To: douglis@sprite.Berkeley.EDU (Fred Douglis) In-reply-to: pkantak@ms.uky.edu (Prashant Kantak) Organization: U.C. Berkeley In article <12402@s.ms.uky.edu>, pkantak@ms (Prashant Kantak) writes: > I am trying to implement process migration on the UNIX operating system >across homogenous (Suns or VAXENS) networked systems. > Could anyone please recommend some good references for the same. (I'll send a copy to the author by e-mail but figured this might interest others as well.) There was an issue of the IEEE Technical Committee on Operating Systems Newsletter (Winter 1989) with a bunch of articles on process migration. This included a system for performing a variant of migration on Unix using checkpoint and restart, like "unexec" for emacs, TeX, and others. I think it would be very difficult to implement vanilla migration on Unix because of things like IP/TCP, shared file descriptors, and so on. If the process's file state must be preserved across migration, you'd have a lot of issues to deal with. If you have a system like LOCUS, with support for file sharing built in, then migration is more feasible. Fred