From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Some state/data file info
Date: Thu, 9 Feb 2012 21:33:38 -0500 [thread overview]
Message-ID: <CAD2Ti2-ggDgRZYA=xGL7qVNHA4BhtkNNVD5yY0ZUcoLwVX_H5g@mail.gmail.com> (raw)
I've been playing with the tools in db 4.8.30, and bitcoin stable...
My blockchain is up to date. Bitcoin is not running.
# strings database/*
This will at times yield the addresses in your wallet.
So it's not exactly in compliance with 'only your wallet file matters'.
Bitcoin always leaves behind at least one "database/log.nnn" file.
Shouldn't it roll and delete it on exit like it does the other state files?
Particularly after a simple "we're able to do nothing but local
operations" invocation
like: bitcoind -proxy=127.0.0.1:9050 -keypool=0 -connect=127.0.0.1
-nodnsseed -noirc
Similarly, the ".lock" file is never deleted.
Shouldn't it be upon exit?
Vacuuming addr, blkindex, and wallet with "db_dump | db_load" will save
significant space. I do not yet know how to view or validate blk0001.dat.
When left with junk, I've been removing everything except:
addr.dat - node addresses
bitcoin.conf - config
blk0001.dat - blocks
blkindex.dat - index to blocks
wallet.dat - wallet
reply other threads:[~2012-02-10 2:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAD2Ti2-ggDgRZYA=xGL7qVNHA4BhtkNNVD5yY0ZUcoLwVX_H5g@mail.gmail.com' \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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