From: Gabriel Diaz Lopez de la Llave <gdiaz@9grid.es>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Fossil+venti install problem
Date: Wed, 9 Jan 2008 19:01:47 +0100 [thread overview]
Message-ID: <5B4FA714-A96B-4402-B142-76E3EC816D3A@9grid.es> (raw)
In-Reply-To: <f344d16dc709562c393fb4c9df4fbd3d@csplan9.rit.edu>
hello
unless the time difference is high there should be no problems iirc
Russ answered this on a thread about timezone changes and venti, the
error message was about arena creation time.
slds.
gabi
On Jan 9, 2008, at 18:46, john@csplan9.rit.edu wrote:
>> On Wed Jan 9 12:05:15 EST 2008, a.verardo@tecmav.com wrote:
>>> Yes. I could, but a reasonable hypothesis is that fossil
>>> issue
>>
>> hypothesis is great. but unless you try something to limit the
>> possbilities, hypothesis is not useful.
>>
>>> a lot of requests caused by a venti unexepected behaviour.
>>> Probably the install procedure is ok.
>>> Could it be an endless backup due to a wrong (interpretation
>>> of the)
>>> sys clock ?
>>
>> why would your clock be different from everone elses?
>>
>> - erik
>
> Doesn't venti get unhappy when your current time is earlier
> than the last-written block or something like that? I thought
> problems could also arise with fossil/venti if you had two
> timesyncs running.
>
> I of course never have any problems because my systems are
> always configured PERFECTLY ;)
>
> John
next prev parent reply other threads:[~2008-01-09 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 17:05 a.verardo
2008-01-09 17:35 ` erik quanstrom
2008-01-09 17:46 ` john
2008-01-09 18:01 ` Gabriel Diaz Lopez de la Llave [this message]
2008-01-10 1:15 ` William S. Morgart
-- strict thread matches above, loose matches on Subject: below --
2008-01-09 14:28 a.verardo
2008-01-09 14:42 ` erik quanstrom
2008-01-09 8:17 a.verardo
2008-01-09 13:11 ` erik quanstrom
2007-12-27 11:10 [9fans] fossil+venti " a.verardo
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=5B4FA714-A96B-4402-B142-76E3EC816D3A@9grid.es \
--to=gdiaz@9grid.es \
--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).