gLite 3.1
glite-SGE_utils - Update to version 3.1.7-0
|
| Date |
14.11.2008 |
| Priority |
Normal |
Description
glite-SGE_utils
glite-info-dynamic-sge and lcg-jobmanager-sge are now prepared to not overwrite manually modified versions of /opt/lcg/libexec/lcg-info-dynamic-sge and /opt/globus/lib/perl/Globus/GRAM/Jobmanager/lcgsge.pm. If this is the case, the new files will be deployed as ".rpmnew" files and must be manually forced by the site admins.
In a running SGE lcg-CE no reconfiguration is needed. Just ensure that /opt/lcg/libexec/lcg-info-dynamic-sge, /opt/glite/etc/gip/plugin/glite-info-dynamic-ce and glite-info-dynamic-scheduler-wrapper have 755 permissions.
For interoperability with other Grid projects, or if one needs to load a specific environment on the WNs not present by default, it's now possible to configure in the jobManager configuration file (lcgsge.conf) a path to a script with the proper environment to load using a variable named *GRID_ENV*( $GRID_ENV = '<path to your script>').
Next time yaim is executed invoking the SGE_utils configuration, glite-yaim-sge-utils functions will store the SGE, JM and IP configurations as .OLD.<count> if different from the implemented defaults. This opens the possibility for the site admin to keep track of its manual changes.
Please also have a look at the list of known issues.
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
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)
|
|
