diff options
| author | grarpamp <grarpamp@gmail.com> | 2012-02-09 21:33:38 -0500 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2012-02-10 02:33:45 +0000 |
| commit | b553c2b0e008b4715dd0b81899ae4b8dc473e903 (patch) | |
| tree | 5aec98ea377d8390b9dcce15203e3ba9ee97553e | |
| parent | b08404aa2d3497b3770c1d878b33f8fb1213ba2c (diff) | |
| download | pi-bitcoindev-b553c2b0e008b4715dd0b81899ae4b8dc473e903.tar.gz pi-bitcoindev-b553c2b0e008b4715dd0b81899ae4b8dc473e903.zip | |
[Bitcoin-development] Some state/data file info
| -rw-r--r-- | 9f/6f86b5c16ca10ce54c74d6a617297fef88f0ad | 84 |
1 files changed, 84 insertions, 0 deletions
diff --git a/9f/6f86b5c16ca10ce54c74d6a617297fef88f0ad b/9f/6f86b5c16ca10ce54c74d6a617297fef88f0ad new file mode 100644 index 000000000..adf88128a --- /dev/null +++ b/9f/6f86b5c16ca10ce54c74d6a617297fef88f0ad @@ -0,0 +1,84 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <grarpamp@gmail.com>) id 1RvgIz-0007GE-M9 + for bitcoin-development@lists.sourceforge.net; + Fri, 10 Feb 2012 02:33:45 +0000 +Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com + designates 74.125.82.175 as permitted sender) + client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com; + helo=mail-we0-f175.google.com; +Received: from mail-we0-f175.google.com ([74.125.82.175]) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1RvgIz-0005ss-0I + for bitcoin-development@lists.sourceforge.net; + Fri, 10 Feb 2012 02:33:45 +0000 +Received: by werc1 with SMTP id c1so2291815wer.34 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 09 Feb 2012 18:33:38 -0800 (PST) +MIME-Version: 1.0 +Received: by 10.180.104.4 with SMTP id ga4mr278460wib.17.1328841218918; Thu, + 09 Feb 2012 18:33:38 -0800 (PST) +Received: by 10.180.103.227 with HTTP; Thu, 9 Feb 2012 18:33:38 -0800 (PST) +Date: Thu, 9 Feb 2012 21:33:38 -0500 +Message-ID: <CAD2Ti2-ggDgRZYA=xGL7qVNHA4BhtkNNVD5yY0ZUcoLwVX_H5g@mail.gmail.com> +From: grarpamp <grarpamp@gmail.com> +To: bitcoin-development@lists.sourceforge.net +Content-Type: text/plain; charset=UTF-8 +X-Spam-Score: -1.0 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (grarpamp[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature + 0.6 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1RvgIz-0005ss-0I +Subject: [Bitcoin-development] Some state/data file info +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Fri, 10 Feb 2012 02:33:45 -0000 + +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 + + |