From: a@9srv.net
To: 9fans@9fans.net
Subject: [9fans] Replica (partly?) stuck in time
Date: Thu, 20 May 2010 01:08:06 -0400 [thread overview]
Message-ID: <4f7a4789fb64737fb7aca1ea23492806@9srv.net> (raw)
On my cpu server, replica seems to be confused over its current
point in time.
When I first ran it today, I got a bunch of (correct) local
conflicts, and several files were updated. I resolved a few of
the local conflicts and re-ran, and while several things worked
fine, some odd behavior started showing.
Replica always tries to update three files, but never actually
does so. There were existing versions of the files; I've tried
removing them and recreating them. Replica notices the changes,
but still won't update them.
(pardon the bunch of -c's below. pull is a function calling
glenda's pull. this is as hostowner.)
cpu% pull -c acme/bin/386 -c 386/9pc -c 386/9load -c 386/bin -c 386/9loaddebug -c 386/9loadlite -c 386/9loadlitedebug -c 386/9pxeload -c 386/9pxeloaddebug -c rc/bin/9fs -c rc/bin/termrc -c rc/bin/cpurc -c rc/bin/cpurc.local -c lib/ndb/auth -c 386/9pc -c 386/9pc.gz -c 386/9pccpu -c 386/9pccpu.gz -c 386/9pcdisk -c 386/9pcdisk.gz -c 386/9pcf -c 386/9pcf.gz -c acme/mail/src
a sys/lib/sysconfig/auth/boundary/httppasswords 660 sys sys 1016833584
! sys/lib/sysconfig/auth/boundary/keys: locally created; will not overwrite
! sys/lib/sysconfig/auth/boundary/netkeys: locally created; will not overwrite
If I leave out the various -c arguments, replica has no idea
I've blessed those files. It's correct that httppasswords
doesn't exist while the other two do. If I give it a -s, It'll
make all three "a" lines; in any case, nothing in that
directory changes.
It is noticing other changes; for example, these two just
showed up in a successive run:
cpu% pull -c acme/bin/386 -c 386/9pc -c 386/9load -c 386/bin -c 386/9loaddebug -c 386/9loadlite -c 386/9loadlitedebug -c 386/9pxeload -c 386/9pxeloaddebug -c rc/bin/9fs -c rc/bin/termrc -c rc/bin/cpurc -c rc/bin/cpurc.local -c lib/ndb/auth -c 386/9pc -c 386/9pc.gz -c 386/9pccpu -c 386/9pccpu.gz -c 386/9pcdisk -c 386/9pcdisk.gz -c 386/9pcf -c 386/9pcf.gz -c acme/mail/src
a sys/lib/sysconfig/auth/boundary/httppasswords 660 sys sys 1016833584
! sys/lib/sysconfig/auth/boundary/keys: locally created; will not overwrite
! sys/lib/sysconfig/auth/boundary/netkeys: locally created; will not overwrite
c sys/man/2/atof
c sys/src/cmd/fossil/cache.c
Those files are indeed updated on my disk, and don't show up
in further replica runs. There are corresponding entries in
/dist/replica/client/plan9.(log db).
I can't find a definition of /dist/replica/client/plan9.time.
I noticed the permissions were weird for that directory (not
writable by hostowner), and the contents seems odd:
1252443603 7182
The first number is in September of last year. I take the
next to be the "gen", although I'm not really clear how to
interpret that. Fixing permissions made no difference.
I'm stumped. Anyone have any ideas?
next reply other threads:[~2010-05-20 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 5:08 a [this message]
2010-05-20 5:45 ` ron minnich
2010-05-20 15:23 ` David Leimbach
2010-05-20 15:24 ` David Leimbach
2010-05-20 15:46 ` ron minnich
2010-05-20 15:48 ` erik quanstrom
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=4f7a4789fb64737fb7aca1ea23492806@9srv.net \
--to=a@9srv.net \
--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).