Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Trouble with gnus-agent-expire
Date: Mon, 28 Sep 2009 14:09:12 -0500	[thread overview]
Message-ID: <87k4ziantz.fsf@newsguy.com> (raw)
In-Reply-To: <87ljjy3ojy.fsf@newsguy.com>

Harry Putnam <reader@newsguy.com> writes:

> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> Hi Harry,
>>
>>> I thought to update gnus to todays cvs.. although it wasn't more than
>>> a few wks old... No change... As it happens I'd updated emacs day
>>> before yesterday (I run the cvs 23 version).
>>
>> Did you try with the gnus version that is included with emacs 23?
>> Basically, that's also No Gnus, but there might be some changes that
>> aren't synchronized back into the Gnus CVS yet.
>
> No, but doing so now... it shows version 5.13.  Its running now and
> chewing up between 94-99 percent of cpu.  No messages show up in echo
> areas it just shows my last command:
>
>    M-x gnus-agent-expire
>
> Its been running for 5 minutes already... doesn't look too promising

I let it run for 15 minutes... it didn't do anything but chew up
resources.

What can I do to get the expiration to happen?

It would be ok with me to just delete all numbered files by hand.  

But I don't want to redownload all that.... 

If I keep nov and .agentview will gnus think things are like they were
and just carry on with new messages?




  reply	other threads:[~2009-09-28 19:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  2:13 Harry Putnam
2009-09-28 10:32 ` Tassilo Horn
2009-09-28 18:35   ` Harry Putnam
2009-09-28 19:09     ` Harry Putnam [this message]
2009-09-28 19:19       ` Tassilo Horn
2009-09-28 20:07         ` Harry Putnam
2009-09-28 20:13           ` Adam Sjøgren
2009-09-29 13:34             ` Harry Putnam

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=87k4ziantz.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    /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).