From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil 'halt' command?
Date: Mon, 13 Apr 2009 19:26:51 -0400 [thread overview]
Message-ID: <ec54f885871452ae412b87c87aee99f8@quanstro.net> (raw)
In-Reply-To: <84f39b4fe2fa4ddabe63c68d966743d4@terzarima.net>
On Mon Apr 13 18:55:24 EDT 2009, forsyth@terzarima.net wrote:
> i'd have thought that soft updates ensure consistency,
> but a halt command ensures that all the changes are actually written.
i think your point is a good one and definately true
(and begs the question of disk caches), but given the paper,
one does wonder. halt didn't show up until here
http://9fans.net/archive/2003/04/218
but there are later notes, e.g.,
http://9fans.net/archive/2003/11/66
that fossil was a bit difficult to shutdown cleanly.
i'm not sure if that was in reference to the chicken-and-egg
nature of the fossil/venti shutdown process or a problem
with fossil.
- erik
prev parent reply other threads:[~2009-04-13 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 11:54 Venkatesh Srinivas
2009-04-13 17:26 ` Charles Forsyth
2009-04-13 23:26 ` 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=ec54f885871452ae412b87c87aee99f8@quanstro.net \
--to=quanstro@quanstro.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).