From: "Kevin Greiner" <kevin.greiner@compsol.cc>
Subject: Re: Huge .overview file -> how to reduce it?
Date: Tue, 7 Feb 2006 23:40:08 -0600 [thread overview]
Message-ID: <200602072340.AA7798838@mail.ev1.net> (raw)
Well, at this point in time, the easiest solution is to simply
delete the .overview file. You'll loose all of your article
headers but the vast majority point to expired articles anyway.
The headers for current articles will simply be downloaded again
the next time you visit the group.
You may want to check the manual to setup agent expiration (not
related to imap expiration) then run gnus-agent-expire
periodically.
Kevin
---------- Original Message ----------------------------------
From: Georges Ko <gko@gko.net>
Date: Mon, 06 Feb 2006 22:26:51 +0800
>Hi!
>
>I have been reading some traffic-intensive groups for one year,
but
>lately, when trying to read the group, I have "Memory exhausted"
>messages when generating the *Summary* buffer...
>
>It turns out that the .overview file of that group has grown to
130 Mb
>with the "head" containing data from one year before, whereas the
>oldest data on my server for this group is from early December...
>
>How can I reduce its size (automatically or something)?
>
>My setup is "No Gnus v0.3" with a NNTP server (Hamster), all on
the
>same Windows 2000 machine.
>
>Thanks!
>
>Georges
>--
> Georges Ko gko@gko.net
2006-02-06
>
>
>
________________________________________________________________
Sent via the EV1 webmail system at mail.ev1.net
next reply other threads:[~2006-02-08 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 5:40 Kevin Greiner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 14:26 Georges Ko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602072340.AA7798838@mail.ev1.net \
--to=kevin.greiner@compsol.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).