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.
Fixed a bug that prevented configuration of OSG-RSV (VDT Ticket 5390)
Updated GIP from 1.1.1 to 1.1.2. (VDT Ticket 5438)
Updated Bestman, SRM-Client-LBNL, and SRM-Tester-LBNL to 220.127.116.11.i6
to fix many bugs. (VDT Ticket 5449)
Updated GUMS-Service and GUMS-Client to 1.3.15 to fix bugs
(VDT Ticket 5450)
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)
The BWCTL and OWAMP packages now set the MANPATH in the
environment so their man pages can be found.
Updated the VDT System Profiler to include some OSG configuration
and installation information.
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)
The VDT updater prints a small note into the vdt-install.log, so it
is clear what changes were caused by the VDT updater.
The vdt-ca-manage usage statement and POD have been updated to be
more consistent with other documentation. (VDT Ticket 5446)
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
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