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.0p22 Update
On 2010-10-19, the VDT team announced the release of VDT 2.0.0p22.
We have streamlined the update procedure to remove some steps including the second
backups. The new update process is available to anyone updating from VDT 2.0.0p21
(OSG 1.2.14) or later.
Updated the Generic Information Provider to version 1.1.12. Information on the changes
is included in the ticket: (VDT Ticket 7741)
Updated the Gratia configuration for the Glexec and GridFTP probes to include
extra attributes in the Gratia ProbeConfig configuration file.
Updated the OSG-Discovery Tools to version 1.0.6.
Added useful exit codes to the vdt-control script. (VDT Ticket 6019) (VDT Ticket 6490)
The new exit codes are documented here.
We changed the default EMAIL_DOMAIN for our Condor installation from $(UID_DOMAIN) to
$(FULL_HOSTNAME). This change can prevent accidentally spamming the mail server of
$(UID_DOMAIN) in some circumstances. (VDT Ticket 5833)
Fixed the MySQL-5 init script that was released in VDT 2.0.0p21. The fix is to
properly create a lock file within VDT_LOCATION. However, we did not observe any
problems starting or stopping MySQL related to this bug.
Fixed a problem that required the XML::Parser Perl module to be pre-installed on
a system before installing the VDT. This bug was introduced in VDT 2.0.0p21.
Note: This change will not affect most sites.
Added an 'accept_limited' option in the Managed Fork section of the config.ini file.
This option was requested by Fermi to use when a gatekeeper is re-forwarding jobs
to other gatekeepers. It will not be commonly used and it will not be present in
the default config.ini file - the default behavior of configure-osg is unchanged.
(VDT Ticket 7757)
If you installed VDT 2.0.0 after VDT 2.0.0p22 was released on
2010-10-19, you do not need to do any of these update operations
because you will have 2.0.0p22.
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.