Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: archiving threads one contributes to
Date: Wed, 23 Jul 2014 17:16:58 +0200	[thread overview]
Message-ID: <87ha282jh1.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.5906.1406127108.1147.info-gnus-english@gnu.org>

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> No. Right now some article are present in my agent
> cache (in
> agent/nntp/news.gwene.org/gmane/emacs/gnus/user). If
> I understand things correctly, these articles may
> expire at some point:
>
>   gnus-agent-expire-days
>   
> The number of days that a ‘read’ article must stay in
> the agent's local disk before becoming eligible for
> expiration (While the name is the same, this doesn't
> mean expiring the article on the server. It just
> means deleting the local copy of the article).
>
> What is also important to understand is that the
> counter starts with the time the article was written
> to the local disk and not the time the article was
> read. Default 7.

I also have that value 7 and all my posts are there,
from way back. Perhaps just because the posts are
marked in certain ways, you still have to issue some
command to have them removed from your disk. I don't
know except I have old posts, lots of them.

> I want to make sure the articles are copied locally
> to some place where they won't expire. However I
> don't want to retain every article posted on these
> newsgroups indefinitely.

Why not? It is just a bunch of text files, all neatly
organized already. My News directory is 5.7M!

If you want to delete the files with discretion,
perhaps you can tell Gnus never to do it (if indeed
Gnus does it for you) and then write a script that
deletes unwanted posts habitually while keeping some,
based on the Message ID and Subject headers I
mentioned.

> It seems the default value is to delete.

I don't know, mine are there. Check your folders, don't
you have old posts?

> And the manual argues against caching everything: "If
> you have an extremely slow NNTP connection, you may
> consider turning article caching on. Each article
> will then be stored locally under your home
> directory. As you may surmise, this could potentially
> use huge amounts of disk space, as well as eat up all
> your inodes so fast it will make your head swim. In
> vodka."

With "caching" do you mean keep local copies on the
disk, i.e., the news ASCII files with digits as names?
(e.g., 5527)?

I don't see how a bunch of such files can do anything
to either disk space or deplete your inode supply.

Try 'df -i' to see if you are running out of inodes, I
have all filesystems one or two percent.

Perhaps that manual entry was written in another time
with small disks/inode filesystems, very enthusiastic
Useneters, and/or or with respect to posts carrying
binary data?

-- 
underground experts united
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2014-07-23 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5872.1406046569.1147.info-gnus-english@gnu.org>
2014-07-22 17:51 ` John Hasler
2014-07-22 18:39   ` Alan Schmitt
     [not found]   ` <mailman.5875.1406054409.1147.info-gnus-english@gnu.org>
2014-07-22 20:38     ` Emanuel Berg
2014-07-23  6:42       ` Alan Schmitt
     [not found]       ` <mailman.5889.1406097766.1147.info-gnus-english@gnu.org>
2014-07-23 14:25         ` Emanuel Berg
2014-07-23 14:51           ` Alan Schmitt
     [not found]           ` <mailman.5906.1406127108.1147.info-gnus-english@gnu.org>
2014-07-23 15:16             ` Emanuel Berg [this message]
2014-07-23 17:36               ` Alan Schmitt
     [not found]               ` <mailman.5920.1406137007.1147.info-gnus-english@gnu.org>
2014-07-23 18:25                 ` Emanuel Berg
2014-07-23 18:52                   ` Alan Schmitt
2014-07-22 16:28 Alan Schmitt

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=87ha282jh1.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).