gLite > gLite 3.1 > glite-SE_dpm_mysql > Update to glite-SE_dpm_mysql 3.1.2-0  
 
 

 

 

gLite 3.1

glite-SE_dpm_mysql - Update to version 3.1.2-0


Date 07.04.08
Priority Normal

Description

DPM 1.6.7-4 update

This update contains the new DPM version with the following bug fixes and new features:
  • group writable directories when SRM started with umask 0 fixed bug #33769: incorrect pool free space after dpm-drain
  • SRM v2 and SRMv2.2 new (fixed) behaviour when creating subdirectories with srmMkdir.
There are two cases worth mentioning for srmMkdir:
  1. The parent directory in which the sub-directories are created do not have default ACLs. In this case the umask of the SRM server matters.
    • before this patch all sub-directories are created with permissions 0755 whatever value has the umask.
    • with this patch, all sub-directories are created with permission 0755 if the default system umas is used (022) or 0775 if the umask in the SRM 2.2 startup script is set to 0.
  2. The parent directory in which the sub-directories are created have default ACLs specifying group writable. The umask is ignored in this case (Posix behaviour).
    • before this patch, all sub-directories are created with permissions 0755
    • with the patch, all sub-directories are created with the permissions set in the default ACL (0775) in our case.


Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #33769 pool free space not updated after filesystem drain/removal
 #34799 DPM: creation of new directories with wrong mask

Updated rpms

Name Version Full RPM name Description
DPM-server-mysql 1.6.7-4sec.slc4 DPM-server-mysql-1.6.7-4sec.slc4.x86_64.rpm DPM MySQL Server
DPM-srm-server-mysql 1.6.7-4sec.slc4 DPM-srm-server-mysql-1.6.7-4sec.slc4.x86_64.rpm SRM MySQL Servers
glite-SE_dpm_mysql 3.1.2-0 glite-SE_dpm_mysql-3.1.2-0.x86_64.rpm gLite metapackage (glite-SE_dpm_mysql)

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Service must be restarted.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)