|
bash-4.1$ ./irodssetup
|
|
iRODS configuration setup
|
|
----------------------------------------------------------------
|
|
This script prompts you for key iRODS configuration options.
|
|
Default values (if any) are shown in square brackets [ ] at each
|
|
prompt. Press return to use the default, or enter a new value.
|
|
|
|
After this completes, other configuration options can be selected by
|
|
editing the config/config.mk file and running 'make' again.
|
|
|
|
A prior iRODS configuration file was found. This script can
|
|
prompt you for changes, or use the same configuration again.
|
|
You can also change parameters by editing config/irods.config
|
|
and restarting this script.
|
|
|
|
Use the existing iRODS configuration without changes [yes]? no
|
|
|
|
|
|
For flexibility, iRODS has a lot of configuration options. Often
|
|
the standard settings are sufficient, but if you need more control
|
|
enter yes and additional questions will be asked.
|
|
|
|
Include additional prompts for advanced settings [no]?
|
|
|
|
|
|
iRODS configuration
|
|
-------------------
|
|
iRODS consists of clients (e.g. i-commands) with at least one iRODS
|
|
server. One server must include the iRODS metadata catalog (iCAT).
|
|
|
|
For the initial installation, you would normally build the server with
|
|
the iCAT (an iCAT-Enabled Server, IES), along with the i-commands.
|
|
|
|
After that, you might want to build another Server to support another
|
|
storage resource on another computer (where you are running this now).
|
|
You would then build the iRODS server non-ICAT, and configure it with
|
|
the IES host name (the servers connect to the IES for ICAT operations).
|
|
|
|
If you already have iRODS installed (an IES), you may skip building
|
|
the iRODS server and iCAT, and just build the command-line tools.
|
|
|
|
Build an iRODS server [no]?
|
|
|
|
|
|
|
|
|
|
|
|
iRODS can make use of the Grid Security Infrastructure (GSI)
|
|
authentication system in addition to the iRODS secure
|
|
password system (challenge/response, no plain-text).
|
|
In most cases, the iRODS password system is sufficient but
|
|
if you are using GSI for other applications, you might want
|
|
to include GSI in iRODS. Both the clients and servers need
|
|
to be built with GSI and then users can select it by setting
|
|
irodsAuthScheme=GSI in their .irodsEnv files (or still use
|
|
the iRODS password system if they want).
|
|
|
|
Include GSI [yes]?
|
|
|
|
The GLOBUS_LOCATION and the 'install type' is needed to find include
|
|
and library files. GLOBUS_LOCATION specifies the directory where
|
|
Globus is installed (see Globus documentation). The 'install type' is
|
|
which 'flavor' of installation you want to use. For this, use the
|
|
exact name of one of the subdirectories under GLOBUS_LOCATION/include
|
|
or 'none' in certain cases (e.g. the install type is 'globus').
|
|
|
|
You also need to set up your Globus GSI environment before running
|
|
this.
|
|
|
|
GLOBUS_LOCATION [/usr/local/globus-c4]?
|
|
|
|
Available types appear to be: globus
|
|
|
|
GSI Install Type to use (or 'none') [globus]?
|
|
|
|
iRODS can make use of the MIT Kerberos authentication
|
|
system in addition to the iRODS secure password system.
|
|
Both the clients and servers need to be built with Kerberos
|
|
and then users can select it by setting
|
|
irodsAuthScheme 'KRB' in their .irodsEnv files (or still use
|
|
the iRODS password system if they want).
|
|
|
|
Include Kerberos [no]?
|
|
|
|
NCCS Auditing extensions (SQL based) can be installed if
|
|
desired. See the README.txt file in server/icat/auditExtensions
|
|
for more information on this.
|
|
|
|
Include the NCCS Auditing extensions [no]?
|
|
|
|
|
|
Confirmation
|
|
------------
|
|
Please confirm your choices.
|
|
|
|
--------------------------------------------------------
|
|
GSI enabled
|
|
GLOBUS_LOCATION /usr/local/globus-c4
|
|
gsiInstallType globus
|
|
|
|
Kerberos not selected
|
|
|
|
NCCS Audit Extensions not selected
|
|
|
|
Build iRODS command-line tools
|
|
--------------------------------------------------------
|
|
|
|
Save configuration (irods.config) [yes]?
|
|
Saved.
|
|
|
|
|
|
Start iRODS build [yes]?
|
|
|
|
|
|
Build and configure
|
|
-------------------
|
|
|
|
Preparing...
|
|
|
|
Configuring iRODS...
|
|
|
|
Step 1 of 4: Enabling modules...
|
|
properties
|
|
ERA
|
|
msoDrivers
|
|
examples
|
|
|
|
Step 2 of 4: Verifying configuration...
|
|
No database configured.
|
|
|
|
Step 3 of 4: Checking host system...
|
|
Host OS is Linux.
|
|
Perl: /usr/bin/perl
|
|
C compiler: /usr/bin/g++ (gcc)
|
|
Flags: none
|
|
Loader: /usr/bin/g++
|
|
Flags: none
|
|
Archiver: /usr/bin/ar
|
|
Ranlib: /usr/bin/ranlib
|
|
64-bit addressing supported and automatically enabled.
|
|
|
|
Step 4 of 4: Updating configuration files...
|
|
Updating config.mk...
|
|
Skipped. No change.
|
|
Updating platform.mk...
|
|
Skipped. No change.
|
|
Updating irods.config...
|
|
Updating irodsctl...
|
|
|
|
Compiling iRODS...
|
|
|
|
Step 1 of 2: Compiling library and i-commands...
|
|
|
|
Step 2 of 2: Compiling tests...
|
|
|
|
Done!
|
|
-----
|
|
|
|
To use the iRODS command-line tools, update your PATH:
|
|
For csh users:
|
|
set path=(/informatique/biscarat/Formation/iRODS/clients/icommands/bin $path)
|
|
For sh or bash users:
|
|
PATH=/informatique/biscarat/Formation/iRODS/clients/icommands/bin:$PATH
|
|
|
|
If you wish to set the ports to use, set the environment variable
|
|
'svrPortRangeStart' or edit the svrPortRangeStart line in irodsctl.pl.
|
|
See the 'Specifying Ports' page on the irods web site for more.
|
|
|
|
For i-commands-only builds like this, irodssetup does not
|
|
attempt to create your ~/.irods/.irodsEnv file, so you need to
|
|
create or update it by hand yourself. See the iRODS web site page
|
|
on the User Environment. You may wish to copy .irodsEnv from
|
|
another host.
|
|
bash-4.1$
|