On 09/30/09 16:00, Tobias J Kreidl wrote: > Nigel, I thought most of the cleanup operation was more or less > automatic, so what does running the script manually bring? Is it for > cases where the DB gets too huge too quickly? Or should one write a > cron job to run > > cbpadmin --cleanup > > once a day?
Maybe I worded the below wrong, it should be run once a day. The frequency is up to you, but 1 day is a good start. -N >> Hrmmm .... v2 is mostly automated in terms of what it cleans out vs. the >> various policies you've setup. >> >> Stuff like quotas & accounting require tracking of mail, which is heavy >> on DB entries if you're doing 1 mil+ per day, by heavy I mean 1 record >> per message (as it tracks all the recipients per message). >> >> I am aware of a few installations 5 mil+ that do cleanup once a day and >> some that do it every hour. Maybe they can reply on this with their >> findings? >> >> v2 does not lock the entire DB, so cleanup taking a few mins or even an >> hour or so doesn't really impact anything. >> >> Try once a day first, it may take a while, then compare it with once an >> hour and compare. If you have any issues I am more than willing to look >> into them for you and work to ensure that cleanup is as fast as possible. >> >> I was thinking about an automated daemon to cleanup the DB depending on >> various stats, so no need for cronjobs. >> >> -N >> >> ------------------------------------------------------------------------ >> > Nigel Kukard wrote: > >>> Does policydv2 include automatic cleanup of older data or is there some >>> other mechanism similar to the policyd-cleanup script from V1? >>> >> Check out cbpadmin script, with --cleanup afaicr off the top of my head. >> >> -N _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
