On Sat, 23 Nov 2002 13:57:56 -0500
David Trask [EMAIL PROTECTED] wrote:
Ok...what about this? Is it possible to restrict the cluster to servers
only? That way you don't transmit the Xserver stuff over the network to
and from the clients thus possibly messing with bandwidth. Can we simply
Ok...what about this? Is it possible to restrict the cluster to servers
only? That way you don't transmit the Xserver stuff over the network to
and from the clients thus possibly messing with bandwidth. Can we simply
build a server cluster that balnces among itself...leaving the client
Short answer as long as the shutdown is clean and teh server in question is not
serving the actuall data filesor home node then migrating process will never know it
is gone. as to a dirty shutdown on teh process needing said node will notice the issue.
Evan
I assume it is not referring to
Hi James,
Thanks for your detail information.
On Sat, 2002-10-26 at 22:04, James Jensen wrote:
Basically the idea is to combine the processing power of all the idle CPU
cycles on the client terminals (since all they are doing is running
Xwindows or a shell if you set them to boot at runlevel
--- Stephen Liu [EMAIL PROTECTED] wrote:
Hi James,
Thanks for your detail information.
On Sat, 2002-10-26 at 22:04, James Jensen wrote:
Basically the idea is to combine the processing power of all the idle
CPU
cycles on the client terminals (since all they are doing is running
Stephen,
Basically the idea is to combine the processing power of all the idle CPU
cycles on the client terminals (since all they are doing is running
Xwindows or a shell if you set them to boot at runlevel 3) with the server.
Kind of similar to having a really big multi-processor SMP box ;-)
--- Stephen Liu [EMAIL PROTECTED] wrote:
On Sat, 2002-10-26 at 21:41, John McCreesh wrote:
If your single server is running out of capacity, one way to expand is
to add additional servers and build an openMosix cluster.
I assume it is not referring to the capacity of hard drive.
