Rich Megginson wrote: > jim at scusting.com wrote: > >> I have noticed on my Fedora consumers there appear to be quite a few >> tombstones going back months even thought the Purge delay is set to a week: >> >> ldapsearch -x -b "cn=mapping tree,cn=config" -D "cn=Directory Manager" >> -W cn=replica nsds5ReplicaPurgeDelay >> # replica, o=blah.com, mapping tree, config >> dn: cn=replica,cn="o=blah.com",cn=mapping tree, cn=config >> nsds5ReplicaPurgeDelay: 604800 >> >> --- example tombstone --- >> # ad82a101-1dd111b2-80a3f995-55bd0000, bob at zzz.com, Blah, blah.com >> dn: nsuniqueid=ad82a101-1dd111b2-80a3f995-55bd0000, >> uid=bob at zzz.com,ou=Blah, o=blah.com >> objectClass: blahPerson >> objectClass: nsTombstone >> uid: bob at zzz.com >> nsParentUniqueId: ccd21704-1dd111b2-80a6a51e-7dae0000 >> modifyTimestamp: 20090713210513Z >> >> There seems to be hundreds of these dating back 6 months to when the >> server was built. Why are these old entries not being purged? >> >> > The purge algorithm never purges everything. How many are not purged? > What's the oldest date? > The oldest date is 13/07/2009 which was when the server was built and the database imported. There are about 200 on that date, there are another 300 spread over the time since then. This server wont be having that many changes so I'm not sure if this would reflect all tombstones since then or not - I suspect there would of been a few more than that if they were never removed. Is there a way to see why these ones were not deleted? Is it possible to manually force a purge of these? Jim.
