From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and rsync
Date: Fri, 05 Nov 2010 19:06:04 +0000 [thread overview]
Message-ID: <87fwvfsi8z.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lj5a2bw7.fsf@invalid.invalid>
nunojsilva@invalid.invalid (Nuno J. Silva) writes:
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
>
>> nunojsilva@invalid.invalid (Nuno J. Silva) writes:
>>
>>> So I've now hit the issue where I have two computers on which I want to
>>> keep gnus stuff on-sync.
>>>
>>> I've tried the simple solution: rsyncing the whole bunch of files (news,
>>> mail, .gnus.el, and some other gnus files.
>>
>> maybe have a look at unison? works very well for keeping systems in
>> sync.
>
> I will, but AFAICT, from the debugging I made today, the issue is not
> rsync, so I'll delay looking unison for a while.
>
> What happens is that, after starting gnus, a lot of NOV files get
> changed.
I found that I had to include .newsrc.eld in the syncing operation
(whether via rsync or unison) but that, for some reason, I also find
that all the nov files get updated and need re-syncing every time. Very
annoying but so far no problems (other than slowness in syncing).
> Next step seems to be understanding which changes are made to NOV files
> so I can know why is this happening...
Please do let us know. I would like to avoid this overhead...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
next prev parent reply other threads:[~2010-11-05 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 22:48 Nuno J. Silva
[not found] ` <87ocaetdmn.fsf@ucl.ac.uk>
[not found] ` <87lj5a2bw7.fsf@invalid.invalid>
2010-11-04 10:35 ` Richard Riley
2010-11-04 23:36 ` Nuno J. Silva
2010-11-05 19:06 ` Eric S Fraga [this message]
2010-11-13 18:27 ` Nuno J. Silva
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=87fwvfsi8z.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--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).