Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide (coming soon)
- Migrating from GT2
- Migrating from GT3
Reference
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces (coming soon)
- Resource Properties
- Samples
- Glossary
- Performance Studies (coming soon)
Manuals
Common Runtime
Security
- Non-WS (General) Security
- WS Java Security
- Message-level
- Authz Framework
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
- SGAS
Data Mgt
MDS4
Execution Mgt
A sample SysV-style
boot script for MyProxy is installed at
$GLOBUS_LOCATION/share/myproxy/etc.init.d.myproxy.
To install on Linux, copy the file to /etc/rc.d/init.d/myproxy and run:
chkconfig --add myproxy
You will need to edit the file to set the GLOBUS_LOCATION environment
variable correctly.
Alternatively, to run the myproxy server out of inetd or xinetd, you need to do the following as root:
- Add the entries in
$GLOBUS_LOCATION/share/myproxy/etc.services.modifications to the/etc/servicesor/etc/inet/servicesfile. - Add the entries in
$GLOBUS_LOCATION/share/myproxy/etc.inetd.conf.modificationsto/etc/inetd.confor/etc/inet/inetd.conf, or copy$GLOBUS_LOCATION/share/myproxy/etc.xinetd.myproxyto/etc/xinetd.d/myproxy. You'll need to modify the paths in the file according to your installation. - Reactivate the inetd (or xinetd). This is typically accomplished by sending the SIGHUP signal to the daemon. Refer to the inetd or xinetd man page for your system.