Description of problem:
/usr/bin/convert_pam_mount_conf.pl does not define the routine callback_lsof, so that when it encounters an lsof file system definition in /etc/security/pam_mount.conf (e.g.

lsof /usr/sbin/lsof %(MNTPT)

)

it dies, leaving an invalid /etc/security/pam_mount.conf.xml file.  This action occurs during the pam_mount package update.

Version-Release number of selected component (if applicable):
0.47-1

How reproducible:
Always.

Steps to Reproduce:
1. configure pam_mount as described with version pam_mount-0.18-2
2. yum update
3.
  
Actual results:

Invalid /etc/security/pam_mount.conf.xml file.  No more home directory.

Expected results:

Valid /etc/security/pam_mont.conf.xml file.  Home directory present.

Additional info:

The convert_pam_mount_conf.pl script worked after I commented out the lsof mount from /etc/security/pam_mount.conf.  I don't remember putting that there myself; I suspect everyone has it.  I'm not familiar with the lsof file sytem, and it appears inessential to the system.  The following patch abandons lsof support:

--- /usr/bin/convert_pam_mount_conf.pl  2008-09-04 23:28:34.000000000 -0400
+++ convert_pam_mount_conf.pl   2008-09-12 21:55:15.000000000 -0400
@@ -81,6 +81,11 @@
        $writer->emptyTag("fsckloop", "device" => $fields[1]);
 }
 
+sub callback_lsof
+{
+       print STDERR "lsof no longer supported";
+}
+
 sub callback_luserconf
 {
        my @fields = @_;