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: Fri, 11 Nov 2005 23:35:48 -0600	[thread overview]
Message-ID: <ufyq24edn.fsf@vignette.com> (raw)
In-Reply-To: <x4iruy8oi9.fsf@footbone.schlitt.net>

wayne <wayne@schlitt.net> writes:

> In <uy83x5j53.fsf@vignette.com> Kevin Greiner <kevin.greiner@vignette.com> writes:
>
>> wayne <wayne@schlitt.net> writes:
>>
>>> 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.
>>>
>>> [...]
>>
>> The cron job is a good idea.  The agent is generating these files
>> because it corrected an error in the overview file.
>
> I saw some discussions about the backup overview files being created
> when errors were detected, so I went and deleted *all* the overview
> files.  The backup files were immediately being created.  So, this
> isn't a case of a rare corruption of the .overview that sticks around.
> Whatever it is, the problem happens very quickly.

Now, that's interesting.  There's quite a few agent users in the world
so this isn't a common issue.  There must be something about the nntp
headers that your server is providing.  There are messages written as
the same time as the backup is created.  Something like 'Duplicate
overview line for ...' or 'Overview buffer not sorted'.  Can you tell
me which message you are seeing?  You might need to look in the
*Messages* buffer to find it.

TIA,
Kevin


  reply	other threads:[~2005-11-12  5:35 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
2005-11-12  4:43   ` wayne
2005-11-12  5:35     ` Kevin Greiner [this message]
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=ufyq24edn.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).