Quick note about the #define RWSPEED

	On some computers, like mine, the check to see whether or not the client
	is running happens so fast that Seti doesn't have time to write its PID
	to the PID file. Thus, the RWSPEED tells the client how long to wait when
	'run' is pressed until it checks for the process. I realize I could probably
	work around this by using pure Unix calls and not Seti's PID file, but
	I don't do this because of the possibility of multiple Seti clients running
	at once. Recently I noticed that the same goes for the lock file. So
	basically you need the RWSPEED to be high enough to allow for disk reads and
	writes. I think :)
