On Thu, Oct 21, 2004 at 04:28:56PM -0400, Colin Walters wrote: > Has anyone else noticed a lot of files being created as .rpmnew with the > latest pam update? I don't recall changing these files... > > warning: /etc/pam.d/other created as /etc/pam.d/other.rpmnew > warning: /etc/security/access.conf created as /etc/security/access.conf.rpmnew > warning: /etc/security/chroot.conf created as /etc/security/chroot.conf.rpmnew > warning: /etc/security/console.perms created as /etc/security/console.perms.rpmnew > warning: /etc/security/group.conf created as /etc/security/group.conf.rpmnew > warning: /etc/security/limits.conf created as /etc/security/limits.conf.rpmnew > warning: /etc/security/opasswd created as /etc/security/opasswd.rpmnew > warning: /etc/security/pam_env.conf created as /etc/security/pam_env.conf.rpmnewwarning: /etc/security/time.conf created as /etc/security/time.conf.rpmnew Hmm, I was wondering why up2date had eaten its sources file. Dave