NAME: netparty.x

				--- SERVER PART ---

SYNOPSIS: cpudataserv port

DESCRIPTION: Cpudataserv will detect the Mhz and free RAM-MB of the
	     machine. It then publishes these data on the local network.

OPTIONS: There is only one option on the server side, nothing very interesting:

	 port: Tells cpudataserv on what port to listen. Cpudataserv will
	       always use tcp/ip ports and listen to them. There is no
	       security at all at that point. Everybody can read the published
	       data. But that should not make the machine more vulnerable.

				--- CLIENT PART ---

SYNOPSIS: control serverlist command/recover count mhz ram

DESCRIPTION: Control queries all servers listed in serverlist for their
	     free resources. It then starts new XTerms with a sshconnections
	     to the most idle hosts. There the command is executed in screens
	     for best crashrecovery. Control must be started with DISPLAY
	     variable set for XTerm able to find its display.

OPTIONS: The options must be given in the same order as explained in here.

	 serverlist: A file with the following information and format:
		     port:ip
		     port:ip
		     port:ip
		        .
			.
			.
		     This file contains information what hosts to contact and
		     on which ports. Take care: If one of these hosts is not
		     accessible, control will stop working.

	 command: This is the command to be executed at the remote host.
	 	  In the special case of command being "recover", screen
		  sessions are reconnected instead of opened newly to
		  make crashrecovery uncomplicated. Control in that case
		  opens count connections to every host instead of only
		  count connections at all, so use this option with care.

	 count: This parameter specifies how many times command should be
	 	executed. In the special case of command being "recover"
		it tells how many connections are opened to one host.

	 mhz: This tells control how many MHz a started command will suck
	      approxymately. Control will substract this value from queried
	      data instead of requery the data to increase performance.

	 ram: The same as MHz but for free MBs of RAM. Control will refuse to
	      start more commands of the RAM limit of an host is reached for
	      swap is much too slow for being used with a gameserver.

AUTHOR: Jens-Wolfhard Schicke, Drahflow, jens.schicke@hvf-bs.net
