From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Using sup on multiple computers?
Date: Fri, 10 Jul 2009 10:30:40 -0400 [thread overview]
Message-ID: <1247236046-sup-9543@Longbow> (raw)
In-Reply-To: <1247194844-sup-6153@sfo.thejof.com>
Excerpts from Jonathan Lassoff's message of Thu Jul 09 23:03:22 -0400 2009:
> Excerpts from Michael Stapelberg's message of Thu Jul 09 17:38:25 -0700 2009:
> > Hi,
> >
> > I'd like to use sup on my notebook and on my workstation. Is there any
> > simple/recommended way to synchronize the index?
>
> As far as I know, this isn't supported in sup yet.
>
> One way I work around this to use sup on two machines is that I know my
> access is mutually exclusive i.e. I don't use more than one host at
> once.
The smarter way of doing this is to keep your .sup on a remote server as
a share and mount it onto the right place in your home when you log in.
This still has the disadvantage of only being able to use one sup at a
time, but at least sup will lock the index using its lockfile, so you
can't accidentally run two at once and screw something up.
It also prevents you from having to manually rsync stuff.
The nicest way to do this would to probably use sshfs. This way, the
index is shared, you only need ssh (no NFS nastiness), it can mount
automatically, and since sup is actually running on your local machine,
it can save attachments just fine.
One note: You need to either have _identical_ imap folders on your
computers in the identical filesystem paths, or you need to have your
mail delivered to the server and share that too.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
next prev parent reply other threads:[~2009-07-10 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 0:38 Michael Stapelberg
2009-07-10 2:57 ` Edward Z. Yang
2009-07-10 10:59 ` Michael Stapelberg
2009-07-10 3:03 ` Jonathan Lassoff
2009-07-10 14:30 ` Andrei Thorp [this message]
2009-07-14 15:43 ` John Bent
2009-07-14 19:33 ` Ben Walton
2009-07-14 19:35 ` Michael Stapelberg
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=1247236046-sup-9543@Longbow \
--to=garoth@gmail.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