9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil+venti continuous disk activity
Date: Thu, 23 Mar 2006 17:43:17 +0000	[thread overview]
Message-ID: <82c890d00603230943n748ca95fq490bbea6b10ae7e5@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180603230936y46e53846u94e225441047dd0@mail.gmail.com>

helllo

i have seen that too in this year.

gabi


On 3/23/06, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> On 3/23/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> > it doesn't write to venti except when doing an archive snapshot,
> > and even during that time fossil itself should respond to requests.
> >
>
> not always. on big dumps (> 3 gigs for my system) fossil will
> eventually block all requests and the system will become unresponsive.
> for example, one will be able to open a new rio window on a terminal,
> but rio will block trying to exec /bin/rc...
>
> that was back in 2003, things may have improved significantly since then :)
>

  reply	other threads:[~2006-03-23 17:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 17:08 Skip Tavakkolian
2006-03-23 17:10 ` Russ Cox
2006-03-23 17:18   ` veritosproject
2006-03-23 17:20     ` Russ Cox
2006-03-23 17:22       ` veritosproject
2006-03-23 17:29         ` Ronald G Minnich
2006-03-23 17:29         ` Gabriel Diaz
2006-03-23 17:30         ` andrey mirtchovski
2006-03-23 17:31         ` Charles Forsyth
2006-03-23 17:36           ` andrey mirtchovski
2006-03-23 17:43             ` Gabriel Diaz [this message]
2006-03-23 18:12               ` veritosproject
2006-03-23 18:51                 ` Charles Forsyth
2006-03-23 17:37           ` Skip Tavakkolian
2006-03-23 17:41             ` Gabriel Diaz
2006-03-23 17:38           ` Russ Cox
2006-03-23 17:16 ` David Leimbach

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=82c890d00603230943n748ca95fq490bbea6b10ae7e5@mail.gmail.com \
    --to=gabidiaz@gmail.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).