From: erik quanstrom <quanstro@quanstro.net>
To: a@9srv.net, 9fans@9fans.net
Subject: Re: [9fans] Replica (partly?) stuck in time
Date: Thu, 20 May 2010 11:48:13 -0400 [thread overview]
Message-ID: <4fe6eb1acee7cede0365f5493693f791@kw.quanstro.net> (raw)
In-Reply-To: <4f7a4789fb64737fb7aca1ea23492806@9srv.net>
> 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?
it sounds like the fact that the plan9.time file doesn't
match the log is the problem. it's not too hard to add
some prints to applylog to figure out why it is making
the decisions it makes. perhaps there's already a verbose
option.
- erik
prev parent reply other threads:[~2010-05-20 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 5:08 a
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 [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=4fe6eb1acee7cede0365f5493693f791@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=a@9srv.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).