From: "KingK.Pan" <KingK.Pan@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] What is the danger if bitcoind startted with -flushwallet=false ?
Date: Thu, 14 Aug 2014 00:27:16 +0800 [thread overview]
Message-ID: <CAPGavA_OmV5N-4fc3EbjoU+UqFSWUY1bfePHtzAvbo9oYu+ghA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
Hi everybody,
I tried to reduce the IO of bitcoind, and I found '-flushwallet=false'.
After trying it, my IO reduced greatly.
But why 'flushwallet' is true by default? Is there any danger if
closing the flush wallet thread?
I lost all my coins in testnet after one crash with
'-flushwallet=false', was this because of no flush wallet thread?
--
Qing Qing Pan
okcoin.com
[-- Attachment #2: Type: text/html, Size: 6569 bytes --]
next reply other threads:[~2014-08-13 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 16:27 KingK.Pan [this message]
[not found] <tencent_6F055A157BDF0BD41143F75A@qq.com>
2014-08-13 20:29 ` [Bitcoin-development] What is the danger if bitcoind startted with -flushwallet=false ? Wladimir
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=CAPGavA_OmV5N-4fc3EbjoU+UqFSWUY1bfePHtzAvbo9oYu+ghA@mail.gmail.com \
--to=kingk.pan@gmail.com \
--cc=bitcoin-development@lists.sourceforge.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