From: Harry Putnam <reader@newsguy.com>
Subject: Retrieve lost messages in agent directory
Date: 14 Feb 2000 11:47:47 -0800 [thread overview]
Message-ID: <m2emafpnvg.fsf@reader.ptw.com> (raw)
I don't think this is a problem that gnus is responsible for. I think it
happened from repeatedly rsyncing the full gnus setup form laptop to
Main machine and vis-versa.
I may have blown it on the command line or not really understand how
rsync works. Or may have even been some other cause. To get to the
punch line:
I have 2900 messages in gnu.emacs.gnus. Only 700+ are displayed in
summary buffer when entered with C-u <RET>. I wonder if there is a
way to get those articles back into the nov files? Seems like it
should be a function similar to nnml-generate-nov-data-bases since the
nov files under agent are wholly owned by gnus.
I couldn't really tell if `gnus-request-regenerate' would help. An 's'
search in gnus-info gives no hits on it. egrepping in *.el files I
found it but could'nt really tell what the heck it does.
Getting back to rsync for a moment:
I hope someone here is well experienced with rsyncing Gnus setup from
place to place. My proceedure has been:
I work and live all week in one city then go home to another city on
weekends or days off etc. When going home I rsync my gnus setup to my
laptop like this (from laptop):
rsync -avz -e ssh reader@<Main-Machine>:/home/reader/Mail/ Mail/
rsync " ditto ditto /News/ News/
Then conclude with:
scp reader@<Main-Machine>:/home/reader/.newsr* .
That copies to and overwrites the current .newsrc .newsrc.eld on
portable machine
Reverse the process when coming back to main machine.
I suspect I may have left off a trailing slash sometime or something
else like that.
I've since written scripts to make it harder to screw it up, but just
wondered if other rsyncers would see a problem in the above proceedure.
next reply other threads:[~2000-02-14 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 19:47 Harry Putnam [this message]
2000-02-14 22:18 ` Kai Großjohann
2000-02-15 7:27 ` Anil B. Somayaji
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=m2emafpnvg.fsf@reader.ptw.com \
--to=reader@newsguy.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).