Re: htdig and sources.redhat.com loadavg

[Hans-Peter Nilsson <hp@bitrange.com>]

On Mon, 5 Apr 2004, Phil Edwards wrote:
> Huh?  If the problem is that the database files are growing larger than
> their limit of 2G -- and that seems to be the issue based on all the old
> mail in my mailbox -- then we look for files that are getting too large:

No, you misunderstood.  There's no need to search around for
files that "grew too large".  Checking the known set of DB files
and see whether one of them is 0x7fffffff bytes long (but I
suggest comparing with a slightly lower number) would give an
improved indication that further attempts to re-index will also
fail so it's no use for the script to retry.  Feel free to
improve the htdig-update script that way if you think it would
improve the situation, but that's not the crontab thing you
suggested.

Still, nothing in that direction will help *now*; it would maybe
help against useless re-indexing attempts if some temporary
measure was taken that'd shrink the DB file to within 2G.  It's
just that I think I've already made all such reasonable
temporary measures in the past.

> > anyway no, you can win this game with a cute crontab entry,
> > except perhaps the change made that prepended an existing one
> > with "#".
>
> Likewise, I can't parse that.

By prepending the existing htdig-update entry with "#", I
disabled it.  The point was that once htdig DB gets "over the
limit", it stays that way.  Re-indexing makes files (at least
temporarily) slightly larger than with a plain update.

brgds, H-P