Software Links
Getting Started
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide
- Migrating Guides
Reference
Manuals
Common Runtime
Security
- GSI C
- GSI Java
- Java WS A&A
- C WS A&A (coming soon)
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
Data Mgt
WS MDS
Execution Mgt
Table of Contents
GridFTP is built and installed as part of a default GT 4.2.0 installation. For basic installation instructions, see Installing GT 4.2.0. No extra installation steps are required for this component.
If you wish to install GridFTP without installing the rest of the Globus Toolkit, refer to the Installing GT 4.2.0 section of the System Administrator's Guide. Perform steps 1-3, as written (Note that you do not need Ant, a JDK, or a JDBC database to build only GridFTP). However, instead of running "make" as directed in step 4,
Run:
globus$ make gridftp
If you wish to have a log file of the build, use tee:
globus$ make gridftp 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
If you wish to install only the GridFTP server, refer to the the Installing GT 4.2.0 section of the System Administrator's Guide. Follow steps 1-3 as written. However, instead of running "make" as directed in step 4,
Run:
globus$ make gpt globus_gridftp_server
If you wish to have a log file of the build, use tee:
globus$ make gpt globus_gridftp_server 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
If you wish to install only the GridFTP client, refer to the the Installing GT 4.2.0 section of the System Administrator's Guide. Follow steps 1-3 as written. However, instead of running "make" as directed in step 4,
Run:
globus$ make globus-data-management-client
If you wish to have a log file of the build, use tee:
globus$ make globus-data-management-client 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
If you wish to install only the GridFTP SDK, refer to the the Installing GT 4.2.0 section of the System Administrator's Guide. Follow steps 1-3 as written. However, instead of running "make" as directed in step 4,
Run:
globus$ make globus-data-management-sdk
If you wish to have a log file of the build, use tee:
globus$ make globus-data-management-sdk 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
If you wish to build a combination of GridFTP elements, refer to the the Installing GT 4.2.0 section of the System Administrator's Guide. Follow steps 1-3 as written. However, instead of running "make" as directed in step 4,
Run:
globus$ make [any combination of the above commands, each separated by a space]
For example, if you just want to install the GridFTP server and client, the command would be:
globus$ make gpt globus_gridftp_server globus-data-management-client
If you wish to have a log file of the build, use tee:
globus$ make [any combination of the above commands, each separated by a space] 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
If you wish to build and install a statically linked set of GridFTP binaries, refer to the Installing GT 4.2.0 section of the System Administrator's Guide. Follow steps 1-2 as written. In step 3, however, you should
Run:
globus$ export GLOBUS_LOCATION=/usr/local/globus-4.0.0
globus$ ./configure --prefix=$GLOBUS_LOCATION --with-buildopts="--static" globus$ make gpt globus_gridftp_server
If you wish to have a log file of the build, use tee:
globus$ make gpt globus_gridftp_server 2>&1 | tee build.log
The syntax above assumes a Bourne shell. If you are using another shell, redirect stderr to stdout and then pipe it to tee.
Starting with Globus 4.2.0, threaded flavor is the default flavor for the GridFTP server. Non-threaded flavor is still the default flavor for the client.
If you are building from a source installer, both threaded and non-threaded flavors of server and client will be built by default.
By default, the server executable in $GLOBUS_LOCATION/sbin is threaded
and the client executable in $GLOBUS_LOCATION/bin is non-threaded.
If you built from the source installer, you will find non-default flavors of both the server and client binaries in
$GLOBUS_LOCATION/sbin/[flavor]/shared and $GLOBUS_LOCATION/bin/[flavor]/shared.
To use those flavors by default, simply copy those binaries to $GLOBUS_LOCATION/sbin or $GLOBUS_LOCATION/bin.
Changing globus-url-copy from non-threaded to threaded:
$ cp $GLOBUS_LOCATION/bin/gcc32dbgpthr/shared/globus-url-copy $GLOBUS_LOCATION/bin
Changing globus-gridftp-server from threaded to non-threaded:
$ cp $GLOBUS_LOCATION/sbin/gcc32dbg/shared/globus-gridftp-server $GLOBUS_LOCATION/sbin
Checking whether a binary is a threaded flavor or not with the tool ldd (no output means non-threaded):
$ ldd $GLOBUS_LOCATION/sbin/globus-gridftp-server |grep thread
libpthread.so.0 => /lib/libpthread.so.0 (0x00cab000)