Note: This version of the VDT (1.10.1) is supported, but is not our latest stable release. The current stable release is 2.0.0.

VDT 1.10.1p Update

On 2008-12-04, the VDT team announced the release of VDT 1.10.1p.

Changes to VDT 1.10.1p

Patched UberFTP so that it doesn't fail with an error with "-a gsi" is passed to it. This option existed in older versions of UberFTP, and some CMS jobs expect it to exist. Passing this argument now results in a warning, not an error. The patch has been passed to the UberFTP developers and will be in a future version of UberFTP. (VDT ticket 4419)
Patched Globus to fix a threading problem that caused stability problems for LFC. As far as we know, it only affected LFC. (VDT ticket 4481) (Globus ticket 6510)

Updating to VDT 1.10.1p

If you installed VDT 1.10.1 after VDT 1.10.1p was released on 2008-12-04, you do not need to do any of these update operations because you will have 1.10.1p.

The best way to do the update is to update the individual packages that have changed. To be clear, we do not recommend using pacman -update without specifying specific package names. Also note that you only need to update packages if you installed them. You can see what packages have been installed with:

pacman -lc

Pre-update directions

Before you do any of the update directions that follow, please run the following commands to stop services and take a backup of your installation. This applies for all of the updates.

cd $VDT_LOCATION
. setup.sh
vdt-control --off
cp -pr $VDT_LOCATION BACKUP-LOCATION

The copy command makes a complete backup of your VDT installation, in case something goes wrong. Do not skip this step!

Updating CA-Certificates

Note: if you have not yet updated your CA-Certificates package (released on September 11th in VDT 1.10.1i), some of the following updates may automatically include this update for you. After this update, you will need to do a one-time configuration to re-install the certificates on your system. Many of the components installed by the VDT will not work until the certificates are re-installed. See the full instructions

1. Updating UberFTP

This step is only for installations that include the UberFTP; look for the file $VDT_LOCATION/globus/bin/uberftp to know if you've installed it.

pacman -update UberFTP

2. Updating Globus

There are potentially two updates to perform for Globus.

This step is only for installations that include the Globus Essentials; look for the file $VDT_LOCATION/globus/bin/grid-proxy-init to know if you've installed it.
```
pacman -update Globus-Base-Essentials
```
This step is only for installations that include the Globus SDK; look for the file $VDT_LOCATION/vdt/etc/package_data/Globus-Base-SDK.filelist to know if you've installed it. Most people have not installed it.
```
pacman -update Globus-Base-SDK
```

Post-update directions

If you are finished applying all lettered updates, do not forget to restart services, typically using vdt-control. For example, to turn on all services:

vdt-control --on