glite-GLEXEC_wn - Updated to version 3.2.5-1
Normal priority update
Released on Update 31 (06/07/2011)
Description (See the patch #4882)
What's new
This update is needed to bring in new versions of the LCMAPS-plugins-pep-c and PEP-API.
- The PEP-API needs updating to fix a randomly occuring time-out when gLExec tries to authorize and the Argus-PEPd-server.
- The LCMAPS-plugin-c-pep needs updating in order to use the new PEP-API library. At the same time, the new plugin can now handle a situation when the X509_USER_PROXY (proxy of pilot job user) is located on an NFS partition with root-squash enabled.
Dependent Patches
| Number | Description |
|---|---|
| There are no dependent patches. | |
Fixed Bugs
| Number | Description |
|---|---|
| #82685 | LCMAPS-plugins-c-pep couldn't read the proxy from an NFS root-squashed file system |
| #82681 | LCMAPS-plugins-c-pep/Argus authorization request times out. |
Updated Rpms (See the full list)
| Name | Version | Full Rpm Name | Description |
|---|---|---|---|
| glite-GLEXEC_wn | 3.2.5-1 | glite-GLEXEC_wn-3.2.5-1.sl5.x86_64.rpm | glite-GLEXEC_wn |
| glite-authz-pep-api-c | 2.0.1-1 | glite-authz-pep-api-c-2.0.1-1.sl5.x86_64.rpm | Thread safe Argus PEP client API for C |
| glite-security-lcmaps-plugins-c-pep | 1.1.4-1 | glite-security-lcmaps-plugins-c-pep-1.1.4-1.sl5.x86_64.rpm | C-PEP |
| glite-security-voms-api-c | 1.9.19-3 | glite-security-voms-api-c-1.9.19-3.sl5.x86_64.rpm | org.glite.security.voms-api-c |
| glite-security-voms-api-cpp | 1.9.19-3 | glite-security-voms-api-cpp-1.9.19-3.sl5.x86_64.rpm | org.glite.security.voms-api-cpp |
| glite-yaim-core | 4.0.14-1 | glite-yaim-core-4.0.14-1.noarch.rpm | YAIM core package |
| gpt | 3.2_4.0.8p1_x86_64_rhap_5-1 | gpt-3.2_4.0.8p1_x86_64_rhap_5-1.x86_64.rpm | The Grid Packaging Tools. This is the version packaged by VDT. |
| gridsite-shared | 1.7.9-3 | gridsite-shared-1.7.9-3.sl5.x86_64.rpm | Gridsite shared rpm |
| lcg-expiregridmapdir | 2.1.0-1 | lcg-expiregridmapdir-2.1.0-1.noarch.rpm | lcg-expiregridmapdir |
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Not needed.