Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 120715 - mail-mta/exim - Add a small cron-script to call exim_tidydb
Summary: mail-mta/exim - Add a small cron-script to call exim_tidydb
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Fabian Groffen
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-28 05:31 UTC by Nico Erfurth
Modified: 2011-12-04 10:42 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Cronscript to call exim_tidydb (exim_tidy,354 bytes, text/plain)
2006-01-28 05:35 UTC, Nico Erfurth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Erfurth 2006-01-28 05:31:45 UTC
exim_tidydb cleans up the files under /var/spool/exim/db, otherwise they will grow  forever ;)
Comment 1 Nico Erfurth 2006-01-28 05:35:04 UTC
Created attachment 78343 [details]
Cronscript to call exim_tidydb

The script reads EXIM_TIDY_TIME from /etc/conf.d/exim and defaults to "7d" if it isn't set. This will be passed to exim_tidydb, so old entries are removed.

The script should pickup all db-files on its own. I use that one on my own server for years, works like a charm.

The script is meant to be placed in /etc/cron.daily
Comment 2 Colin Morey (RETIRED) gentoo-dev 2008-12-07 14:52:35 UTC
Support will be added in exim-4.69-r3 (with a slightly edited patch)
Comment 3 Torsten Veller (RETIRED) gentoo-dev 2009-06-24 13:33:11 UTC
Reassign to net-mail herd as peitolm retires
Comment 4 Eray Aslan gentoo-dev 2011-05-06 20:21:43 UTC
Re-assigning.
Comment 5 Fabian Groffen gentoo-dev 2011-12-04 10:42:08 UTC
I believe creating a cron-script is hard, because one doesn't know if cron is there, what cron, etc.

Instead I added a hint linking to
  http://www.exim.org/exim-html-current/doc/html/spec_html/ch50.html#SECThindatmai

I hope that encourages people to investigate themselves what's the best course of action for their system configuration.  (I didn't know about this myself, and haven't run it for years on my installations, yet I didn't have humongous db files or something, so it seems not to be so problematic to me.)

I close this bug as fixed because of the einfo added to 4.77.  Feel free to reopen if you disagree this is a "fix".