History File over 2GB

[bill davidsen]

In article <yl1y8g459c.fsf at windlord.stanford.edu>,
Russ Allbery  <rra at stanford.edu> wrote:
| 
| bill davidsen <davidsen at tmr.com> writes:
| 
| > I'd like to a single access interface for all the delete functions,
| > since this seems to be done from cancel, buffer rollover, etc.
| 
| Yup, agreed.  I'm not sure the best way to handle real-time deletions from
| CNFS rollover; somehow, SMstore would have to return a list of tokens that
| went away, and I'm not sure how you manage to trace from that to overview
| entries.  We don't really have good data structures to enable this right
| now.

We might need a token to msgid table, and a table with Xref info per
msgid. Then you could relatively quickly find the info to delete. But as
much thrashing as that might seem, it still needs to be done sometime,
either by expire or by a realtime (more or less) cleanup. If entries
could be marked DELETED in overview the delete need not involve a
rewrite of information each time, a daemon could slowly do any final
cleanup, and overview in database would just delete the record.
 
-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.