Welcome to condor_install.  You are going to need to answer a few
questions about how you want Condor configured on this machine, what
pool(s) you want to join, and if this machine is going to serve as
the Central Manager for its own pool.  If you are unsure about how to
answer any of the questions asked here, please consult the INSTALL
file or the Installation chapter of the Condor Administrator's Manual.

The installation is broken down into various steps.  Please consult the
INSTALL file to refer to a specific step if you have trouble with it.

For most questions, defaults will be given in []'s.  To accept the
default, just press return.

If you have problems installing or using Condor, please consult the
Condor Administrator's Manual, which can be found on the World Wide
Web at: http://www.cs.wisc.edu/condor/manual/
If you still have problems, send email to condor-admin@cs.wisc.edu.

Press enter to begin Condor installation


***************************************************************************
        STEP 1: What type of Condor installation do you want?
***************************************************************************

Would you like to do a full installation of Condor? [yes] 

Press enter to continue. 

***************************************************************************
        STEP 2: How many machines are you setting up for Condor?
***************************************************************************

Are you planning to setup Condor on multiple machines? [yes] 
Will all the machines share files via a file server? [yes] no

You will need to run condor_install locally on each machine.
Setting up host "terpcondor" for Condor.

Press enter to continue. 
***************************************************************************
        STEP 3: Install the Condor "release directory", which holds
        various binaries, libraries, scripts and files used by Condor.
***************************************************************************

I can't find a complete Condor release directory.

Have you installed a release directory already? [no] 

Where would you like to install the Condor release directory?
[/usr/local/condor] /export/condor/condor-6.6.10
That directory doesn't exist, should I create it now? [yes] 
Installing a release directory into /export/condor/condor-6.6.10 ... 
etc/
etc/examples/
etc/examples/README
etc/examples/condor.generic
etc/examples/condor_config.local.central.manager
etc/examples/condor_config.local.dedicated.resource
etc/examples/condor_config.local.dedicated.submit
etc/examples/condor_config.local.ckpt.server
etc/examples/condor_config.local.root.ckpt.server
etc/examples/condor_config.local.view_server
etc/examples/condor_config.generic
etc/examples/condor_config.root.generic
etc/examples/condor_config.submit.generic
etc/examples/condor.boot
include/
include/user_log.README
include/user_log.c++.h
include/condor_event.h
include/condor_holdcodes.h
include/file_lock.h
include/condor_constants.h
include/chirp_client.h
src/
src/chirp/
src/chirp/chirp_client.c
src/chirp/chirp_client.h
lib/
lib/libcondorapi.a
lib/condor_rt0.o
lib/libcondorsyscall.a
lib/libz.a
lib/libcondorzsyscall.a
lib/libc.a
lib/libnss_files.a
lib/libnss_dns.a
lib/libresolv.a
lib/libcomp_libgcc.a
lib/libcomp_libstdc++.a
lib/libcomp_libgcc_eh.a
lib/ld
lib/real-ld
lib/Condor.pm
lib/CondorJavaWrapper.class
lib/CondorJavaInfo.class
lib/scimark2lib.jar
lib/Chirp.jar
lib/libchirp_client.a
bin/
bin/condor_cod
bin/condor_config_val
bin/condor_userprio
bin/condor_findhost
bin/condor_history
bin/condor_qedit
bin/condor_version
bin/condor_wait
bin/condor
bin/condor_checkpoint
bin/condor_vacate
bin/condor_reschedule
bin/condor_stats
bin/condor_status
bin/condor_dagman
bin/condor_submit_dag
bin/condor_userlog
bin/condor_q
bin/condor_rm
bin/condor_hold
bin/condor_release
bin/condor_submit
bin/condor_prio
bin/condor_compile
bin/condor_run
bin/condor_glidein
sbin/
sbin/condor_preen
sbin/condor_advertise
sbin/condor_fetchlog
sbin/condor
sbin/condor_on
sbin/condor_off
sbin/condor_checkpoint
sbin/condor_vacate
sbin/condor_restart
sbin/condor_reconfig
sbin/condor_reconfig_schedd
sbin/condor_reschedule
sbin/condor_master_off
sbin/condor_ckpt_server
sbin/condor_shadow.std
sbin/condor_starter.std
sbin/condor_startd
sbin/condor_schedd
sbin/condor_negotiator
sbin/condor_collector
sbin/condor_master
sbin/condor_starter.pvm
sbin/condor_pvmd
sbin/condor_pvmgs
sbin/condor_shadow.pvm
sbin/condor_install
sbin/condor_configure
sbin/condor_init
sbin/condor_updates_stats
sbin/condor_gridmanager
sbin/gahp_server
sbin/grid_monitor.sh
sbin/condor_starter
sbin/rsh
sbin/condor_gridshell
sbin/condor_shadow
man/
man/man1/
man/man1/condor_advertise.1
man/man1/condor_checkpoint.1
man/man1/condor_compile.1
man/man1/condor_configure.1
man/man1/condor_config_val.1
man/man1/condor_findhost.1
man/man1/condor_glidein.1
man/man1/condor_history.1
man/man1/condor_hold.1
man/man1/condor_master.1
man/man1/condor_master_off.1
man/man1/condor_off.1
man/man1/condor_on.1
man/man1/condor_preen.1
man/man1/condor_prio.1
man/man1/condor_q.1
man/man1/condor_qedit.1
man/man1/condor_reconfig.1
man/man1/condor_reconfig_schedd.1
man/man1/condor_release.1
man/man1/condor_reschedule.1
man/man1/condor_restart.1
man/man1/condor_rm.1
man/man1/condor_run.1
man/man1/condor_stats.1
man/man1/condor_status.1
man/man1/condor_store_cred.1
man/man1/condor_submit.1
man/man1/condor_submit_dag.1
man/man1/condor_updates_stats.1
man/man1/condor_userlog.1
man/man1/condor_userprio.1
man/man1/condor_vacate.1
done.

Using /export/condor/condor-6.6.10 as the Condor release directory.

Press enter to continue. 

***************************************************************************
        STEP 4: How and where should Condor send email if things go wrong?
***************************************************************************

If something goes wrong with Condor, who should get email about it?
[root@terpcondor.umiacs.umd.edu] root@umiacs.umd.edu

What is the full path to a mail program that understands "-s" means
you want to specify a subject? [/bin/mail] 

Using /bin/mail to send email to root@umiacs.umd.edu

Press enter to continue. 

***************************************************************************
        STEP 5: Filesystem and UID domains.
***************************************************************************

To correctly run all jobs in your pool, including ones that aren't relinked
for Condor, you must tell Condor if you have a shared filesystem, and if
so, what machines share it.

Please read the "Configuring Condor" section of the Administrator's manual
(in particular, the section "Shared Filesystem Config File Entries")
for a complete explaination of these (and other, related) settings.

Do all of the machines in your pool from your domain ("umiacs.umd.edu")
share a common filesystem? [no] 

Configuring each machine to be in its own filesystem domain.

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] 

Configuring each machine to be in its own uid domain.

Press enter to continue. 

***************************************************************************
        STEP 6: Java Universe support in Condor.
***************************************************************************

Enable Java Universe support? [yes] 

I wasn't able to find a valid JVM.

Please enter the full path to the JVM, or "none" to leave unconfigured:
/opt/j2sdk1.4.2/bin/java

You entered: /opt/j2sdk1.4.2/bin/java
Is that right? [no] yes

Checking to see if you have a Sun JVM...yes.

Using JVM /opt/j2sdk1.4.2/bin/java for Java universe support.

Press enter to continue. 

***************************************************************************
        STEP 7: Where should public programs be installed?
***************************************************************************

The Condor binaries and scripts are already installed in:
        /export/condor/condor-6.6.10/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 /export/condor/condor-6.6.10/bin
to their PATH or explicitly 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] /usr/bin

Press enter to continue. 

***************************************************************************
        STEP 8: What machine will be your central manager?
***************************************************************************

What is the full hostname of the central manager?
[terpcondor.umiacs.umd.edu] 

Your central manager will be on the local machine.

Press enter to continue. 

***************************************************************************
        STEP 9: Where will the "local directory" go?
***************************************************************************

Condor will need to create a few directories for its own use

You have a "condor" user on this machine.  Do you want to put all the
Condor directories in /export/homes/condor? [yes] no

Do you want to put all the Condor directories in
/export/condor/condor-6.6.10/home? [yes] no

Where do you want the Condor directories?
/export/condor-var

Creating all necessary Condor directories ... done.

Press enter to continue. 

***************************************************************************
        STEP 10: Where will the local (machine-specific) config files go?
***************************************************************************

Condor allows you to have a machine-specific config file that overrides
settings in the global config file.

You must specify a machine-specific config file.

Should I put a "condor_config.local" file in /export/condor-var?
[yes] 
Creating config files in "/export/condor-var" ... done.

Configuring global condor config file ... done.
Created /export/condor/condor-6.6.10/etc/condor_config.

Press enter to continue. 

Setting up terpcondor.umiacs.umd.edu as your central manager

What name would you like to use for this pool?  This should be a
short description (20 characters or so) that describes your site.
For example, the name for the UW-Madison Computer Science Condor
Pool is: "UW-Madison CS".  This value is stored in your central
manager's local config file as "COLLECTOR_NAME", if you decide to
change it later.  (This shouldn't include any " marks).
UM College Park

Setting up central manager config file /export/condor-var/condor_config.local ..
. done.

Press enter to continue. 

***************************************************************************
        STEP 11: How do you want Condor to find its config file?
***************************************************************************

Condor searches a few locations to find it main config file. The first place
is the envionment variable CONDOR_CONFIG. The second place it searches is
/etc/condor/condor_config, and the third place is ~condor/condor_config.

Should I put in a soft link from /export/homes/condor/condor_config to
/export/condor/condor-6.6.10/etc/condor_config [yes] 

Installing links for public binaries into /usr/bin ... done.

Press enter to continue. 

***************************************************************************
Condor has been fully installed on this machine.
***************************************************************************

/export/condor/condor-6.6.10/sbin contains various administrative tools.
If you are going to administer Condor, you should probably place that
directory in your PATH.

To start Condor on any machine, just execute:
/export/condor/condor-6.6.10/sbin/condor_master

Since this is your central manager, you should start Condor here first.

Press enter to continue. 

You should probably setup your machines to start Condor automatically at
boot time.  If your machine uses System-V style init scripts, look in
/export/condor/condor-6.6.10/etc/examples/condor.boot
for a script that you can use to start and stop Condor.

Please read the "Condor is installed... now what?" section of the INSTALL
file for things you should do before and after starting the Condor daemons.
In particular, you might want to set up host/ip access security.  See the
Adminstrator's Manual for details.