From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] replica question
Date: Fri, 18 Nov 2011 10:10:52 +0100 [thread overview]
Message-ID: <CAOEdRO04cwvjRzmKWVSMBufykKL_CT+XMZS3XFSJZ8O3HRco+w@mail.gmail.com> (raw)
Hello,
Yesterday I read replica(8), played with it a bit, and I have the
following question:
Say I have a directory A which I—from time to time—want to replicate
to directory B. With replica/updatedb I maintain two files, A.db and
A.log, describing the situation in the A directory.
If A.log has existed since the time replica/updatedb was run for the
first time, I may use this log as an input to replica/applylog and
create a replica of A in B.
However, I don't understand what one should do if this log was removed
or somehow shortened (so that it does not mention the files' addition
anymore). Some such shortening is, I believe, reasonable, since after
say 10 years nobody is probably interested in all the files' changes.
But, if I understand, it is exclusively the log itself (i.e., not the
server database file A.db) that is used for synchronization by
replica...
Is there any more thorough explanation somewhere describing how replica works?
Thank you for hints/explanation!
Ruda
next reply other threads:[~2011-11-18 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 9:10 Rudolf Sykora [this message]
[not found] <CAOEdRO04cwvjRzmKWVSMBufykKL_CT+XMZS3XFSJZ8O3HRco+w@mail.gmail.c>
2011-11-18 13:40 ` erik quanstrom
2011-11-18 15:59 ` Rudolf Sykora
[not found] ` <CAOEdRO0COVcbuVsUd_1Wd1QyDU-jE_kPccfv36N5_sCZBaay=Q@mail.gmail.c>
2011-11-18 19:25 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 17:03 Antonin Vecera
2008-07-06 17:29 ` Pietro Gagliardi
2008-07-06 18:07 ` Antonin Vecera
2008-07-06 18:31 ` Martin Neubauer
2008-07-06 19:00 ` Antonin Vecera
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=CAOEdRO04cwvjRzmKWVSMBufykKL_CT+XMZS3XFSJZ8O3HRco+w@mail.gmail.com \
--to=rudolf.sykora@gmail.com \
--cc=9fans@9fans.net \
/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).