From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Stale NFS using nnmaildir
Date: Thu, 31 Oct 2002 12:48:54 -0500 [thread overview]
Message-ID: <m3y98eo5wj.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <i74k7k0j9om.fsf@math4.unice.fr>
maggesi@math4.unice.fr (Marco.MAGGESI) wrote:
> One more question: is it safe to sync two maildir folders hosted in
> different machines (using rsync or unison[1])? I think so, just asking
> to be sure.
If you make changes sometimes on one machine and sometimes on the
other, you might have difficulty determining which side is right at
any given time. But assuming you can figure that out, and assuming
you sync things so that all the contents of the maildir, including
.nnmaildir/*, are the same, you should be fine. Beware that nnmaildir
uses lots of hard links; if your copying tool creates new files
instead, you'll be using lots more inodes.
paul
next prev parent reply other threads:[~2002-10-31 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <i74smypzcnj.fsf@math4.unice.fr>
2002-10-29 16:42 ` Paul Jarc
[not found] ` <i74k7k0j9om.fsf@math4.unice.fr>
2002-10-31 17:48 ` Paul Jarc [this message]
[not found] <833cqqmqxe.fsf@login.math.unifi.it>
2002-10-30 5:55 ` those who know me have no need of my name
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=m3y98eo5wj.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).