Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: pgnus expiry?
Date: 13 Dec 1998 00:05:49 -0500	[thread overview]
Message-ID: <glmzp8szl5e.fsf@caffeine.mitre.org> (raw)

Am I the only one for whom expiry has ceased to do anything useful?

For a while I thought that I had broken it myself, but after some
experimentation, I don't believe that is the case.

For example... my toplevel topic has the total-expire parameter set to 
t, and my emacs subtopic has expiry-wait set to 14.  I have messages
in my ding group that are much more than two weeks old.  Dating back
to things sent fairly early in the pgnus cycle, in fact.

(The fact that I set the group parameters in the topics has nothing to 
do with the problem, really.)

Invoking expiry simply gives the "Expiring messages in nnml:ding...done" 
message, doesn't delete anything, and then finishes.  Quite quickly.

As much as I appreciate the speedup in expiry speed, disk isn't quite
that cheap.  Any ideas?

-- 
Justin Sheehy

In a cloud bones of steel.
  




             reply	other threads:[~1998-12-13  5:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-13  5:05 Justin Sheehy [this message]
1998-12-13  8:17 ` Karl Eichwalder
1998-12-13  9:04 ` Lars Magne Ingebrigtsen
1998-12-13 11:21 ` Hrvoje Niksic
1998-12-13 18:12   ` Justin Sheehy

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=glmzp8szl5e.fsf@caffeine.mitre.org \
    --to=justin@linus.mitre.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).