gLite 3.1
glite-LFC_mysql - Update to version 3.1.28-0
|
Date |
18.02.2010 |
Priority |
Normal |
Description
glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-TORQUE_client, glite-WN
New version of Yaim Core
New site-info variables
- UNPRIVILEGED_GRIDMAPFILE per VO: This variable was before
defined per site and now it can be configured per VO.
- USER_HOME_PREFIX per VO: This variable was before defined per
site and now it can be configured per VO.
- EDG_HOME_DIR, EDGINFO_HOME_DIR and BDII_HOME_DIR: The home
directories of system accounts can be now be configured. The
suggestion is to define them as /var/lib/user_name but YAIM has
left the default under /home.
- GRIDFTP_CONNECTIONS_MAX: It has been increased from 50 to
150.
- Variables that were wrongly implemented in previous yaim
releases are now fixed: CONFIG_GRIDMAPDIR and
USER_HOME_PREFIX.
New functions
- config_myproxy_libs: new function to be able to configure the
new myproxy server and clients.
- New SAGA adapters: There's a new function called
config_glite_saga that configures the SAGA gLite adapters.
Fixes
- Some libraries have been added to LD_LIBRARY_PATH and
ld.so.conf to be able to configure lcg CE and cream CE in
SL5.
- grid environment cleaning mechanism to be able to install
different WN tarball versions in the same machine.
- YAIM doesn't fail when gLite version package is not
installed. This is useful for non gLite software using YAIM.
- siteinfo packaging is now fixed (-p option).
glite-FTA_oracle, glite-FTS_oracle, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-WN
New version of lcg-vomscerts
This patch introduces a new version of lcg-vomscerts that adds the next cert for lcg-voms.cern.ch and
removes old certs for cclcgvomsli01.in2p3.fr and
vo.racf.bnl.gov
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|