Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: which gnus files used to hold gnus state? (for manual)
Date: Fri, 16 May 2003 16:43:20 -0500	[thread overview]
Message-ID: <uy916mutj.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84d6iin27t.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> John Owens <jowens@ece.ucdavis.edu> writes:
>
>> I'd like to get a list of the files used to hold gnus state. This is
>> for potential inclusion in the manual (after discussion with Lars)
>> and would be important for users who are interested in synching the
>> gnus state of two machines (say, a laptop and a desktop).
>

snip...

>
> Now, for the agent.  There is a subdir ~/News/agent/lib which
> contains the categories and the servers files.  Further subdirs are
> for servers/groups.  (Presumably the exact directory layout depends
> on some *-use-long-file-name(s) variable.)  A directory for a server
> contains a subdir agent.lib with the file agent.lib/active.  All
> other subdirs are groups (in foo.bar or foo/bar format).  Each group
> contains a file .agentview and a file .overview and the messages.
>
> What does .agentview contain? --> Anyone?

The .agentview contains per-article timestamps that are used by the
agent's expiration mechanism.

The .overview file contains the article headers.

>> The overall goal would be to know exactly what files to sync if I want
>> to mirror my gnus setup on computer B from computer A. Hopefully in
>> the next generation of gnus there will be a list of state-containing
>> files and an automated way to sync them (gnus-sync-state-files with a
>> configurable sync command like "rsync -e ssh ..."). This could be
>> useful for users who use a laptop and want to sync before going on
>> the road.
>
> Nifty.
>

snip ...

> So, it boils down to this: if you transfer .newsrc.eld, you got to
> transfer the whole hog.  If you abstain from .newsrc.eld, then you
> can do the some-groups trick alluded to for nnml and nnfolder (and
> probably nnmaildir).

But your seen marks are in .newsrc.eld.  If you don't include it, how
will you know which articles have been read?

> Stuff from cache and agent aren't mentioned in .newsrc.eld, so there
> is no problem.

There's no problem so long as the two machines are sharing the same
servers.  The article files in both the agent and the cache are named
after the article number.  You'll get garbage if you try to use these
files with any server except the one from which they were fetched (I
realize that this isn't what you proposed.  I just want to make sure
that anyone reading this understands).

> Above, when I say .newsrc.eld, I always also mean .newsrc.

Kevin



  parent reply	other threads:[~2003-05-16 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  5:54 John Owens
2003-05-16 19:03 ` Kai Großjohann
2003-05-16 20:50   ` Andreas Fuchs
2003-05-16 21:43   ` Kevin Greiner [this message]
2003-05-17 17:12     ` Kai Großjohann
2003-05-20 18:10   ` Ted Zlatanov

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=uy916mutj.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).