From: Sam Stickland (sam_ml_at_spacething.org)
Date: Mon 10 Nov 2003 - 13:07:59 GMT
>From what I've read of the project, migratable network sockets don't yet
appear to be supported, along with shared memory (Distributed Shared Memory
is still on the Todo list, which also means that programs compiled with
pthreads aren't supported either).
However, if a process can't migrate under OpenMosix then it just doesn't
migrate, rather than crash.
It might be possible to migrate a whole context at once though, without
needing DSM, but moving the whole address space attached to a single
I'm still not convinced of the usefulness of this with though, especially
with the added complexity it entails. It would appear to be a lot easier to
distribute vservers amongst machines manually, and use load-balancers where
appropiate and it would certainly be faster at present time.
----- Original Message -----
Sent: Monday, November 10, 2003 11:35 AM
Subject: Re: OT: Re: [Vserver] Vserver + OpenMosix...
> On Mon, Nov 10, 2003 at 07:06:17PM +1100, Charles Dale wrote:
> > Re: CHPOSX thing, it looks pretty cool. But I fail to see how it would
> > particularly useful for a vserver running typical hosting tasks such as
> > server & mail. Is Apache going to be very happy to be knocked out, find
> > awake on a different machine and then try to keep talking with the
> > was talking to before?? I'd crash myself if I found open network sockets
> > disappearing all around me... Or is there something I'm missing?
> no, you are not missing anything... We would just have to make sure that
> the connections are not dropped/lost. One way could be to allow old
> connections to close on the old machine, and new on the new. Or move
> them while running.
> Vserver mailing list
Vserver mailing list