From: Michael Widerkrantz <mc@hack.org>
To: info-gnus-english@gnu.org
Subject: Re: Maildir as simultaneous spool and backend.
Date: Thu, 15 Mar 2007 10:34:55 +0100 [thread overview]
Message-ID: <8664924zpc.fsf@tim.hack.org> (raw)
In-Reply-To: <m3ps7blmag.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> I don't recommend running more than one Gnus simultaneously. Gnus
> keeps some state information that isn't stored in the maildirs, or
> isn't always kept synchronized with the disk state while it's
> running.
You might be interested in using gnus-slave, though. From the manual:
Each subsequent slave Gnusae should be started with `M-x
gnus-slave'. These slaves won't save normal `.newsrc' files, but
instead save "slave files" that contain information only on what
groups have been read in the slave session. When a master Gnus
starts, it will read (and delete) these slave files, incorporating
all information from them. (The slave files will be read in the
sequence they were created, so the latest changes will have
precedence.)
> Personally, I keep a single Gnus running under screen, and use
> screen -x to reconnect to it.
Me too for my home Gnus, but I usually use screen -rd.
prev parent reply other threads:[~2007-03-15 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 18:25 usenet_spam
2007-03-14 18:20 ` Paul Jarc
2007-03-14 19:01 ` usenet_spam
2007-03-15 9:34 ` Michael Widerkrantz [this message]
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=8664924zpc.fsf@tim.hack.org \
--to=mc@hack.org \
--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).