9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica error
Date: Tue,  8 May 2007 20:11:56 -0400	[thread overview]
Message-ID: <20070509001156.C79491E8C3A@holo.morphisms.net> (raw)
In-Reply-To: <68fadd6d73be654d56169551c54c54dc@quintile.net>

> I am getting an unusual error from replica when I try to
> do a pull from the the labs,  looking the source I am not
> clear what is happening or what to do about it.
> 
> 	term% replica/pull -v /dist/replica/network -s 386/bin/aquarela
> 	post...
> 	stopped updating log apply time because of lib/video.specs
> 	386/bin/aquarela: locally modified; will not update
> 
> I have a seccond server that is perfectly happy so I assume
> I have corrupted my local state.
> 
> Anyone any thoughts or should I delve deeper into replica?

The context here is that the log apply time
marks the point in /dist/replica/client/plan9.log
where the system is up-to-date.  Future pulls
start there in the log.  If you specify only a
subset of the files to pull then this time does
not get updated if there is a file in the remainder
of the log that would need to be copied but is not
specified in the list of files to process.

That prompts the question, where did I specify
a list of files to process?  The answer is that 
the argument you have given as /dist/replica/network
is the first non-option argument, so -s and 386/bin/aquarela
are taken as two more non-option arguments.
The correct command line is

	replica/pull -v -s 386/bin/aquarela /dist/replica/network

or just

	pull -v -s 386/bin/aquarela

using /usr/glenda/bin/rc/pull.  The latter exists mainly
so that you don't have to remember the former.

Russ



      reply	other threads:[~2007-05-09  0:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 23:02 [9fans] (no subject) Steve Simon
2007-05-09  0:11 ` Russ Cox [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=20070509001156.C79491E8C3A@holo.morphisms.net \
    --to=rsc@swtch.com \
    --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).