public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail•com>
To: grarpamp <grarpamp@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Manual file cleanup on exit, safe? [coredump backtrace]
Date: Sat, 16 Jun 2012 01:11:39 +0200	[thread overview]
Message-ID: <20120615231138.GA30505@vps7135.xlshosting.net> (raw)
In-Reply-To: <CAD2Ti292gfPvxR42k-1dMRg_7=oU8WkWdYBxi0f4884vOQ-XCQ@mail.gmail.com>

On Fri, Jun 15, 2012 at 04:58:55PM -0400, grarpamp wrote:
> When bitcoind exits cleanly, it does not seem safe for the blockchain
> to clean up the following hierarchy with rm -r ?

Use -detachdb if you want to detach the blockchain database files from the
database environment at exit. This was turned off by default in 0.6.0 to
speed up the shutdown process very significantly, and few people have a need
to manually fiddle with their blockchain database files.

-- 
Pieter



      reply	other threads:[~2012-06-15 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 20:58 grarpamp
2012-06-15 23:11 ` Pieter Wuille [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=20120615231138.GA30505@vps7135.xlshosting.net \
    --to=pieter.wuille@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=grarpamp@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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