From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] setting up replica.
Date: Mon, 11 Oct 2004 12:04:24 +0100 [thread overview]
Message-ID: <772d66dacfa5ba74333cb75dfc12f0af@quintile.net> (raw)
In-Reply-To: <Pine.BSI.4.58.0410102145370.15930@malasada.lava.net>
A the log and db files must exist (IE you must touch(1) them)
but their contents is maintained by the replica tools.
The proto file describes which files/dirs under the replica
clientroot/serverroot you want to be replicated. You must write
this yourself, though it is fully documented, see proto(2).
As you want to replicate between many machines you might be better
off with nemo's repl which was published on here on 9fans recently,
repl appears to be a peer-to-peer rather than client-server system,
though I don't know any other differences (over to you Capt'n ?)
-Steve
next prev parent reply other threads:[~2004-10-11 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 7:48 Tim Newsham
2004-10-11 11:04 ` Steve Simon [this message]
2004-10-11 19:55 ` Tim Newsham
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=772d66dacfa5ba74333cb75dfc12f0af@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.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).