VDT logo
Search:

(Powered by Google)

Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

VDT 2.0.0p3 Update

On 15 June 2009, the VDT team announced the release of VDT 2.0.0p3.

Changes to VDT 2.0.0p3

  1. Fixed a bug that prevented configuration of OSG-RSV (VDT ticket 5390)
  2. Updated GIP from 1.1.1 to 1.1.2. (VDT ticket 5438)
  3. Updated Bestman, SRM-Client-LBNL, and SRM-Tester-LBNL to 2.2.1.2.i6 to fix many bugs. (VDT ticket 5449)
  4. Updated GUMS-Service and GUMS-Client to 1.3.15 to fix bugs (VDT ticket 5450)
  5. Extended the VDT-Client package (which is the basis for the OSG client package) and the OSG-CE package so that they include the clients for NDT, NPAD, BWCTL, and OWAMP. These are network diagnostic tools that were added in VDT 2.0.0p0 (the initial release). They were requested by ATLAS, and it is desired that they are widely available so that when they are network problems, tools that can help the diagnosis are readily available. (VDT ticket 4400)
  6. The BWCTL and OWAMP packages now set the MANPATH in the environment so their man pages can be found.
  7. Updated the VDT System Profiler to include some OSG configuration and installation information.
  8. The osg-supported-vo-list.txt now uses the lower case name (instead of the mixed case name) and is sorted alphabetically, as suggested by John Weigand. (VDT ticket 5437)
  9. The VDT updater prints a small note into the vdt-install.log, so it is clear what changes were caused by the VDT updater.
  10. The vdt-ca-manage usage statement and POD have been updated to be more consistent with other documentation. (VDT ticket 5446)

Updating to VDT 2.0.0p3

If you installed VDT 2.0.0 after VDT 2.0.0p3 was released on 15 June 2009, you do not need to do any of these update operations because you will have 2.0.0p3 or later.

Recommended method: VDT Updater

We strongly encourage users to update the VDT using the VDT updater script: VDT updater instructions.

Not recommended: Pacman update

If you really want to do it the hard way, instructions for updating by using Pacman directly are available on another page. This method is hard to follow and error prone.