If you've unpacked the Condor tarball somewhere central, you can log on to the client, cd to that directory, and run this command:
condor_install --type=execute,submit --local-dir=/dir/condor/hosts/myclient --central-manager=myserver.example.com --verboseNote that you need to specify the client name (for --local-dir) and the manager name. (If you didn't unpack the files centrally, you'll have to copy the release tarball somewhere appropriate and add a --install=/path/to/condorrelease.tar option.)
As with the server, set the CONDOR_CONFIG variable, and execute /dir/condor/sbin/condor_master to start the Condor daemon! Check it's running by grepping the process list for condor_* processes.
Once you've got everything up and running, you may want to set up a start script so that Condor starts automatically on boot in the future.
You probably also want to have a look at the rules that govern when a job can be run on a client. These are in Part 3 of the global config file. The file sets the "UWisc - CS Dept" rules (look for the definition of UWCS_WANT_SUSPEND in the config file). The rules as defined here are probably a good start -- you can adjust them later if you start having problems, or you can override them for a particular machine if need be.
OK, now you have your server and your first client set up. In the next part of this piece we'll look at how to submit a job.
This article was first published on LinuxPlanet.com.