Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Thu, 12 Aug 2004 18:48:35 +0200	[thread overview]
Message-ID: <iluzn502tgc.fsf@latte.josefsson.org> (raw)
In-Reply-To: <jk47js49w4q.fsf@W003275.na.alarismed.com>

"Steven E. Harris" <seh@panix.com> writes:

>> Is there a simple recipe for reproducing this?
>
> Here's my workflow:
>
> o At work, start Gnus in plugged mode. Read e-mail all day.
>
> o At the end of the day, by way of an rsync-dependent script, send all
>   my changed score files, ~/.newsrc, and ~/.newsrc.eld files to my
>   ISP's disk.
>   Note that I don't sync the agent directories. My understanding is
>   that those are for local cache management. As I want to have a
>   different cache at home, I leave it to Gnus to figure out the
>   appropriate caching operations.

I'm not completely sure, but there might be a problem with your
workflow.  The .newsrc.eld contain active info, and the agent may be
using the active info to decide which headers to download.  So what is
happening is pretty much this:

1. (work machine) active range in .newsrc is 1-4711, which match agent
   overview's.

2. (home machine) active range in .newsrc is 1-4711 (by way of rsync),
   which might not match agent overview's, because they were created
   when the active range was 1-4000 (yesterday).

3. (home machine) as you read new e-mail, the active range increase to
   1-5711, and the agent overview include 4711-5711 data.

4. (work machine) active range in .newsrc is 1-5711 (by way of rsync)
   but agent overview only has 1-4711.  the agent trusts 1-5711 and
   assumes 4711-5711 doesn't exist, and doesn't try to download them
   again.

In other words, you need to sync .overview too.

You may need to sync .agentview as well, but then again you might need
to _not_ sync .agentview.

In the worst case, there is some information in .agentview that need
to be rsync'ed and some information that need to not be rsync'ed.  If
so, we should probably try to separate the data that is local state,
i.e. cache directory, from the .newsrc state data.

If someone recalls exactly how the data in .agentview is used by the
agent, that would answer whether you need to sync it or not.  I don't
recall.

Perhaps you need to take a step back to solve this:

Exactly why are you syncing .newsrc* at all?

Messages flags are supposed to be synchronized via the IMAP server, so
there's no need to synchronize the files for them.  Most other data
that is stored in .newsrc.eld can be stored in .emacs or .gnus.  The
only major thing, that I recall, is that Topics structures can't be
defined except by via .newsrc.eld.

Getting rid of .newsrc.eld would be nice.  Move all setup related
things to .gnus, and all state data into ~/News or wherever they
belong.




  reply	other threads:[~2004-08-12 16:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson [this message]
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris
2004-08-16 19:54         ` Steven E. Harris
2004-08-17 11:39         ` Steinar Bang

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=iluzn502tgc.fsf@latte.josefsson.org \
    --to=jas@extundo.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).