1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
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 <rdwnj@yahoo.com>) id 1VQUR4-0001cH-PX
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Sep 2013 03:46:14 +0000
X-ACL-Warn:
Received: from nm17-vm7.bullet.mail.gq1.yahoo.com ([98.137.177.231])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1VQUR3-00082o-B0
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Sep 2013 03:46:14 +0000
Received: from [98.137.12.190] by nm17.bullet.mail.gq1.yahoo.com with NNFMP;
30 Sep 2013 03:46:07 -0000
Received: from [98.137.12.246] by tm11.bullet.mail.gq1.yahoo.com with NNFMP;
30 Sep 2013 03:46:07 -0000
Received: from [127.0.0.1] by omp1054.mail.gq1.yahoo.com with NNFMP;
30 Sep 2013 03:46:07 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 381935.25104.bm@omp1054.mail.gq1.yahoo.com
Received: (qmail 94180 invoked by uid 60001); 30 Sep 2013 03:46:06 -0000
X-YMail-OSG: Iz1wWZIVM1lMTi31WSPQ2.KhSiVr7VLhaO_EDJSCvaNvCO0
mql0RomJArQkrkAZvBgDha8.UZZHdAANyOTyiES1UtcuKWfiaRKoy8EUQFIG
cdt4A7dWXLczUy8BCzflMCgeitfD_3kt4wIaMXAHNGbBOqsI6_kV7jqsozCB
BzLWjXEb033C8m90rVsAXFdIXEVXBYzNS_jGAnrZezIqi4h3KDN7aiKtEls8
HR2nYee.UubGBAkFdyK7BM5Wb1V9TkZuH77_2oSZFCs4yBOxpmPF0bTmOkbz
T.y690Kl8dtjv9_zZX7ByTqqhXq2llVDQtbzYcrmJ7VaXLwevMjSbrtq9ET4
rGOex6qjeYqO44xYiKzfG6epezSAsVZvqYqG95GCmZahNC.YFH4zoxONydO1
2ucQTyHzHddYN8XkXQ2CG9GJHelnxK5_oWRB2NYVvaxv9ldA5iF41ETX35Ku
DfVEYE5WFvfkO3g2cEc377_bYqv1fqq9miRqYwNg_gUXevHaNHnUPT2Y2S6y
HY5bUqrepQV4NEFzyAJhlYCnqW2si5utp4eBp..YqZQMwGq7uMIizbKMJ9QJ
HqKO16zO4VeXBQ3AXmu3urO2QIMNH11pGYNuG_OZCrxBqrouGtkJyd3EaxZS
0Hp.TSA0LS3sg2Z7zWLNJh8UqCzoigXo-
Received: from [69.126.245.179] by web124502.mail.ne1.yahoo.com via HTTP;
Sun, 29 Sep 2013 20:46:06 PDT
X-Rocket-MIMEInfo: 002.001,
SGVsbG8KCklzIGl0IHJlcXVpcmVkLCBwcmVzdW1lZCwgYXNzdW1lZCwgY29pbmNpZGVuY2UsIGNoYW5jZSBvciBpcnJlbGV2YW50IHRoYXQgdGhlIHRocmVlIGRpZmZlcmVudCBkYXRhYmFzZXMgaW4gYml0Y29pbjoKMS4gdGhlIG5ldHdvcmsgYWRkcmVzc2VzIGRhdGFiYXNlLCByZWZsZWN0ZWQgaW4gcGVlcnMuZGF0CjIuIHRoZSBsZXZlbERCIGJsb2NrIGNoYWluIGRhdGFiYXNlIChibG9ja3MvYmxrbm5ubm4uZGF0LCBibG9ja3MvcmV2bm5ubm4uZGF0LCBibG9ja3MvaW5kZXgvbm5ubm4uc3N0IGV0IGFsLCABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
Message-ID: <1380512766.92704.YahooMailNeo@web124502.mail.ne1.yahoo.com>
Date: Sun, 29 Sep 2013 20:46:06 -0700 (PDT)
From: Ron <rdwnj@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="-626213187-509447910-1380512766=:92704"
X-Spam-Score: 2.1 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.6 HK_RANDOM_ENVFROM Envelope sender username looks random
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(rdwnj[at]yahoo.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.137.177.231 listed in list.dnswl.org]
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?98.137.177.231>]
-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bitcoin.it]
1.0 HTML_MESSAGE BODY: HTML included in message
-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
X-Headers-End: 1VQUR3-00082o-B0
Subject: [Bitcoin-development] locks and directories
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Ron <rdwnj@yahoo.com>
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: Mon, 30 Sep 2013 03:46:14 -0000
---626213187-509447910-1380512766=:92704
Content-Type: text/plain; charset=us-ascii
Hello
Is it required, presumed, assumed, coincidence, chance or irrelevant that the three different databases in bitcoin:
1. the network addresses database, reflected in peers.dat
2. the levelDB block chain database (blocks/blknnnnn.dat, blocks/revnnnnn.dat, blocks/index/nnnnn.sst et al, chainstate/nnnnn.sst et al)
3. the Berkeley DB wallet database (db.log, wallet.dat, database/log.nnnnnnnnn1)
are all in the "datadir" directory?
I only ask since it would seem that a more mature (?) bitcoind or bitcoin-qt would optionally, like the three (databases) in separate paths or drives, etc. It would seem easier to transport, backup etc. the pieces one wants. I find the block chain database is the most important (time consuming), because of its size, to duplicate and transport in order to backup. This also attacks the "Criticism" section in
https://en.bitcoin.it/wiki/Bitcoin-Qt
The first question is: can one backup by just looking at the dates, and just back up those files with the equal or newer dates, and the "log, current and manifest" files? An initial then incremental backups, as it were.
I am thinking of the frailties of data on OS's such as Windows in the hands of the "less than adept" shall we say. Also if one takes part in backing up one's data, one may actually have some idea where it is!
Ron
---626213187-509447910-1380512766=:92704
Content-Type: text/html; charset=us-ascii
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Hello<br><br>Is it required, presumed, assumed, coincidence, chance or irrelevant that the three different databases in bitcoin:<br>1. the network addresses database, reflected in peers.dat<br>2. the levelDB block chain database (blocks/blknnnnn.dat, blocks/revnnnnn.dat, blocks/index/nnnnn.sst et al, chainstate/nnnnn.sst et al)<br>3. the Berkeley DB wallet database (db.log, wallet.dat, database/log.nnnnnnnnn1)<br>are all in the "datadir" directory?<br><br>I only ask since it would seem that a more mature (?) bitcoind or bitcoin-qt would optionally, like the three (databases) in separate paths or drives, etc. It would seem easier to transport, backup etc. the pieces one wants. I find the block chain database is the most important (time consuming), because of its size, to duplicate and transport in order to backup. This also
attacks the "Criticism" section in <br>https://en.bitcoin.it/wiki/Bitcoin-Qt<br><br>The first question is: can one backup by just looking at the dates, and just back up those files with the equal or newer dates, and the "log, current and manifest" files? An initial then incremental backups, as it were.<br><br>I am thinking of the frailties of data on OS's such as Windows in the hands of the "less than adept" shall we say. Also if one takes part in backing up one's data, one may actually have some idea where it is!<br><br>Ron<br><br></div></body></html>
---626213187-509447910-1380512766=:92704--
|
