Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: problem: .overview~[0-9]*~ files not being deleted
Date: Wed, 09 Nov 2005 20:30:48 -0600	[thread overview]
Message-ID: <uy83x5j53.fsf@vignette.com> (raw)
In-Reply-To: <x41x1xjh5s.fsf@footbone.schlitt.net>

wayne <wayne@schlitt.net> writes:

> Ok, I have a wierd one that I hope someone has heard of before.  I've
> poked around some, but I can't find the cause.  I confess I haven't
> dug deeply into the code though.
>
> A while back, I suddenly started to accumulate old .overview~[0-9]*~
> files in my ~/News/agent/ subdirectories.  They stick around for ever,
> so it isn't just keeping the last 4 files.  They seem to accumulate in
> most groups, but maybe not all of them.
>
> I think this started happening when I upgraded to gnus "No gnus v0.4",
> but I'm not certain.  It took a while before I noticed that my disk
> was overflowing with them.  I'm running Debian Linux and uxing "XEmacs
> 21.4 (patch 17) \"Jumbo Shrimp\" [Lucid] (i386-debian-linux) of Sat
> May 28 2005 on penell" 
>
>
> Other than the accumulation of these .overview files, things seem to
> be working fine.
>
>
> Any ideas?  Should I just create a cron job to delete them?

The cron job is a good idea.  The agent is generating these files
because it corrected an error in the overview file.  The original idea
was to keep them around to help with diagnosing the error.
Limiting the agent to a couple of backup files sounds like a good
idea.  I'll see about getting that in the next few days.

Kevin


  reply	other threads:[~2005-11-10  2:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04  2:11 wayne
2005-11-10  2:30 ` Kevin Greiner [this message]
2005-11-12  4:43   ` wayne
2005-11-12  5:35     ` Kevin Greiner
2005-11-12 13:20       ` wayne
2005-11-13  4:17         ` Kevin Greiner
2005-11-13 17:27           ` wayne

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=uy83x5j53.fsf@vignette.com \
    --to=kevin.greiner@vignette.com \
    /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).