Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: More expire/adaptive thoughts/questions
Date: 25 Oct 1996 08:59:12 +0100	[thread overview]
Message-ID: <x6zq1biien.fsf@eyesore.no> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 24 Oct 1996 15:51:25 +0100

Wesley.Hardaker@sphys.unil.ch writes:

> Ok, to quote the manual:
> 
>     By the way, that line up there about Gnus never expiring
>     non-expirable articles is a lie.  If you put `total-expire' in the
>     group parameters, articles will not be marked as expirable, but
>     all read articles will be put through the expiry process.  Use
>     with extreme caution.
> 
> 1) Why is this a bad idea (ie, why extreme caution)?

It isn't a bad idea -- it's a good idea.  You should really know what
you're doing before using it, though.

> 2) One guess:  does it zap cached or ticked articles?

The cache is orthogonal to expiry; and ticked articles aren't read.
So, no.

> 3) If I do something like, say,
>      find ~/News/nnml/group -name '[0-9]*' -atime +14 -exec rm {} \;
>    What does this do to gnus?  IE, is it possible to run a expire cron
>    job safely?  Or does this mess up the active/overview files?

The NOV file lines won't be expired properly.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-10-25  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-24 14:51 Wesley.Hardaker
1996-10-25  7:59 ` Lars Magne Ingebrigtsen [this message]
1996-10-25 12:07   ` Wesley.Hardaker
1996-10-26 14:24     ` Lars Magne Ingebrigtsen
1996-10-28  7:35       ` Wesley.Hardaker

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=x6zq1biien.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).