Policyd 1.80 on a Centos 4.8 server with Mysql Server 4.1.22 A couple of days ago i made a "TRUNCATE TABLE triplet" because this table has grown to few GBytes
I have a crontab to made the cleanup process every hour: Mar 17 10:01:01 xxxxxx cleanup: clean up process starting: policyd v1.80 Mar 17 10:01:01 xxxxxx cleanup: connecting to mysql database: 127.0.0.1 Mar 17 10:01:01 xxxxxx cleanup: connected.. Mar 17 10:01:01 xxxxxx cleanup: expiring validated records older than 60 days (1263632461) Mar 17 10:01:01 xxxxxx cleanup: expired: 0 records Mar 17 10:01:01 xxxxxx cleanup: expiring unvalidated records older than 2 days (1268643661) Mar 17 10:01:01 xxxxxx cleanup: expired: 2637 records Mar 17 10:01:01 xxxxxx cleanup: expiring blacklisted records (1268816461) Mar 17 10:01:01 xxxxxx cleanup: expired: 0 records Mar 17 10:01:01 xxxxxx cleanup: expiring autowhitelisted records older than 90 days (1268816461) Mar 17 10:01:01 xxxxxx cleanup: expired: 0 records The size of the table increase every day and today it's over 20 MB: # ls -lhat triplet.* -rw-rw---- 1 mysql mysql 22M Mar 17 10:03 triplet.MYD -rw-rw---- 1 mysql mysql 18M Mar 17 10:03 triplet.MYI Which is the best way to reduce or control the triplet table size? Best Regards Andrea _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
