I would really like to see expire gone

bill davidsen davidsen at tmr.com
Thu Jan 23 23:09:38 UTC 2003


  I would really like to consider using a database for history instead
of the process we have.  There are several problems in what we have, and
now that the real message-id is not in the file one less benefit. The
problem lies with the expire itself, not the implementation. A faster,
better, more wonderful expire would still (a) run once a day, (b)
occasionally confuse the hell out of programs with history open when
expire runs, and (c) still take twice as much disk as it needs to. Not
to mention requiring me to justify said disk space to byte-sucking
accounting monitors every few years.

  Has someone looked into this, and if so are there any notes on why it
isn't (shouldn't be) done with a database allowing nice gradual
deletions as the articles vanish, and no changes in service centered on
one part of the day?

  I'm looking for info right now, I might sit down and do so tests if I
don't get some good reasons why it can't work with a database.
-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


More information about the inn-workers mailing list