Installation of condor: Create user and group condor. Download condor software from http://www.cs.wisc.edu/condor/downloads/ Do all the following as root. # tar zxvf condor-6.2.1-linux-x86-glibc21.tar.gz # cd condor-6.2.1 # ./condor_install Would you like to do a full installation of Condor? [yes] Are you planning to setup Condor on multiple machines? [yes] Will all the machines share files via a file server? [yes] What are the hostnames of the machines you wish to setup? (Just type the hostnames, not the fully qualified names. Put one machine per line. When you are done, just hit enter.) ouhep1 ouhep2 Have you installed a release directory already? [no] Where would you like to install the Condor release directory? [/usr/local/condor] That directory doesn't exist, should I create it now? [yes] If something goes wrong with Condor, who should get email about it? [root@ouhep1.nhn.ou.edu] hs@mail.nhn.ou.edu What is the full path to a mail program that understands "-s" means you want to specify a subject? [/bin/mail] Do all of the machines in your pool from your domain ("nhn.ou.edu") share a common filesystem? [no] yes Do all of the users across all the machines in your domain have a unique UID (in other words, do they all share a common passwd file)? [no] yes In some cases, even if you have unique UIDs, you might not have all users listed in the password file on each machine. Is this the case at your site? [no] yes The Condor binaries and scripts are already installed in: /usr/local/condor/bin If you want, I can create some soft links from a directory that is already in the default PATH to point to these binaries, so that Condor users do not have to change their PATH. Alternatively, I can leave them where they are and Condor users will have to add /usr/local/condor/bin to their PATH or explicity use a full pathname to access the Condor tools. Shall I create links in some other directory? [yes] Where should I install these files? [/usr/local/bin] What is the full hostname of the central manager? [ouhep1.nhn.ou.edu] You have a "condor" user on this machine. Is the home directory for this account (/home/condor) shared among all machines in your pool? [yes] Do you want to put all the Condor directories for each machine in subdirectories of /home/condor/hosts? [yes] Do you want to specify a local partition for file locking? [yes] Where should I put the lock files? [/var/lock/condor] /var/lock/condor does not exist. Shall I create it now? [yes] Do you want all the machine-specific config files for each host in one directory? [yes] What directory should I use? [/usr/local/condor/etc] Setting up ouhep1.nhn.ou.edu as your central manager What name would you like to use for this pool? OUHEP Should I put in a soft link from /home/condor/condor_config to /usr/local/condor/etc/condor_config [yes] /usr/local/condor/sbin contains various administrative tools. If you are going to administer Condor, you should probably place that directory in your PATH. Be sure to run condor_init on each machine in your pool to create the lock directory before you start Condor there. To start Condor on any machine, just execute: /usr/local/condor/sbin/condor_master Since this is your central manager, you should start Condor here first. ------------ End of condor_install script ------------- Now run condor_init on all machines: [root@ouhep1 root]# /usr/local/condor/sbin/condor_init [root@ouhep2 root]# /usr/local/condor/sbin/condor_init This created empty local config files which should really be sym links to the local config files condor_install created. Also, it made root the owner of several files and directories. Therefore: # cd /home/condor # chown condor.condor condor_config # chown condor.condor hosts # cd hosts # chown condor.condor ouhep* # rm ouhep1/condor_config.local ; \ ln -s /usr/local/condor/etc/ouhep1.local ouhep1/condor_config.local # rm ouhep2/condor_config.local ; \ ln -s /usr/local/condor/etc/ouhep2.local ouhep2/condor_config.local # chown condor.condor ouhep*/condor_config.local Also, all condor executables and daemons seem to be runnable as any user, so turn that off, since only root should be able to do that: # chmod o-x /usr/local/condor/sbin/condor* For some reason, in /usr/local/condor/etc/condor_config, LOCAL_CONFIG_FILE was set to $(LOCAL_DIR)/condor_config.local rather than $(RELEASE_DIR)/etc/$(HOSTNAME).local , so I changed that. So in the future, the local config files should be set correctly by condor_init, namely appear in /usr/local/condor/etc. Also, limit condor read and write access to local domain only: in /usr/local/condor/etc/condor_config , change HOSTALLOW_READ and HOSTALLOW_WRITE from "*" to *.nhn.ou.edu (and *.cs.wisc.edu for read access to condor people). Also, copy condor script from /usr/local/condor/etc/examples/condor.generic to /usr/local/bin/condor (remove soft link there first, if it's there), and change $default_pool=""; to $default_pool="default"; and %configlocation = ( ); to %configlocation = ( "default", "/usr/local/condor/etc/condor_config", ); Then start condor first on ouhep1 then ouhep2: [root@ouhep1 root]# /usr/local/condor/sbin/condor_master [root@ouhep2 root]# /usr/local/condor/sbin/condor_master To add new nodes, also add them to /usr/local/condor/etc/roster . To check: # condor_status To startup on boot: # cp -p /usr/local/condor/etc/examples/condor.boot /etc/rc.d/init.d/condor # ln -s /etc/rc.d/init.d/condor /etc/rc.d/rc3.d/S95condor # ln -s /etc/rc.d/init.d/condor /etc/rc.d/rc5.d/S95condor # ln -s /etc/rc.d/init.d/condor /etc/rc.d/rc0.d/K04condor # ln -s /etc/rc.d/init.d/condor /etc/rc.d/rc6.d/K04condor Do full install of condor_compile script (on all machines): # mv /usr/bin/ld /usr/bin/ld.real # cp -p /usr/local/condor/lib/ld /usr/bin/ld Also, remove x for regular users on all /usr/local/condor/sbin/condor* binaries: chmod o-x /usr/local/condor/sbin/condor* And limit HOSTALLOW_[READ,WRITE] in /usr/local/condor/etc/condor_config to *.nhn.ou.edu