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.0p27 Update
On 2011-06-30, the VDT team announced the release of VDT 2.0.0p27.
VDT-Cleanup is a new Pacman package to help do filesystem cleanup.
The package will be available in any CE installs. More information
is available at
The Globus Gatekeeper can now be run at lower priority using 'nice'. Although the
gatekeeper process is shortlived this priority level will be inherited by all the
children processes it spawns. For more information on setting the nice level of
services on the VDT see this documentation.
The default nice level remains the same as before (is is '0').
A random sleep has been added to the Globus fork jobmanager poll function
to prevent unwanted synchronization when there are many Condor-G grid_monitors.
Condor job manager has been extended to be able to set accounting groups.
(VDT ticket #5838)
SGE job manager changed to use a more reliable method of polling job status.
(VDT ticket #8493)
Bestman, SRM-Client-LBNL, and SRM-Tester-LBNL have been updated to
Configure-osg has improved error message reporting to be more helpful. Also, the
issue of setting the RSV Gratia collector in two places has been resolved. A
warning has been added when the gratia metric probe is set in the Gratia section.
The proper spot to configure this is in the RSV section using the report_to setting
Fixed a bug in the RSV CA certificates probe that triggered when a monitoring site
had CA certificates installed in the same directory as the remote site it was monitoring.
Condor-Cron's init script will now place a lockfile in /var/lock/subsys when running on
Changed behavior of vdt-control to start services up in correct order if
dependencies are specified in state file via
This solves VDT ticket #9248
The Bestman 2 Client is now part of the VDT-Client. However, it's
not in the environment by default. To get it into the
environment. You need to source the environment:
If you installed VDT 2.0.0 after VDT 2.0.0p27 was released on
2011-06-30, you do not need to do any of these update operations
because you will have 2.0.0p27.
Recommended method: VDT Updater
We strongly encourage users to update the VDT using the VDT updater
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.