From: "Roland Winkler" <winkler@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: synchronizing gnus sessions on multiple computers
Date: Tue, 05 Oct 2021 23:28:50 -0500 [thread overview]
Message-ID: <87ee8ydbel.fsf@gnu.org> (raw)
In-Reply-To: <87k0joqew2.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 10 Sep 2021 14:50:21 -0700")
On Fri, Sep 10 2021, Eric Abrahamsen wrote:
> Yes, the .newsrc.eld file only gets written when you save Gnus ("s" in
> the *Group* buffer), and I would absolutely not try to update files for
> a Gnus that's still running, it will not handle that gracefully. It
> should, however, be enough to shut Gnus down first (you can see the
> `gnus-clear-system' function to see what happens then), rsync, then
> restart Gnus.
Thanks, it took me a while to get back to this. It seems that
`gnus-clear-system' / quitting gnus is missing
`gnus-save-newsrc-file-last-timestamp'. Quitting gnus, then rsync'ing
gnus followed by a restart of gnus will use .newsrc.eld file from the
other machine. But when this .newsrc.eld file is saved again, the
timestamp of the file on disk is compared against the old timestamp of
the old file that's already gone.
I submitted a bug report (bug#51052).
next prev parent reply other threads:[~2021-10-06 4:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 23:21 Roland Winkler
2021-09-10 4:46 ` Pankaj Jangid
2021-09-10 11:06 ` Leo Butler
2021-09-10 19:45 ` Bob Newell
2021-09-10 21:15 ` Roland Winkler
2021-09-10 21:50 ` Eric Abrahamsen
2021-09-10 22:39 ` Bob Newell
2021-09-11 4:04 ` Roland Winkler
2021-10-06 4:28 ` Roland Winkler [this message]
2021-10-06 14:42 ` Eric Abrahamsen
2021-09-11 16:07 ` Greg Farough
2021-09-12 18:30 ` Bob Newell
2021-09-12 4:47 ` James Thomas
2021-10-06 4:29 ` Roland Winkler
2021-10-09 4:00 ` James Thomas
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=87ee8ydbel.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=eric@ericabrahamsen.net \
--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).