I think there may be an ideal order of ops bug around rescan, wallet upgrades/import and last block markers.
I dropped an old wallet in a current blockchain. First ran - in rescan mode. It said old walletver. Then rescanned whole chain. AddToWallet some blockhash, blocks out of range, invalid/nonwallet txid's, which were already in there as legit ones in the old logs. Second run in plain mode. New wallet ver logged. Rescanned the last 20k blocks or so, which might have been the marker last time the old wallet was used. Third and later runs... duplicates the second. Never did say 'upgrading wallet' as it sometimes does. Running detach=1 always. Why scan the last 20k every time? Shouldn't have to if whole chain was scanned. And certainly no more than once if not. Also... Dumping the run params (bitcoin.conf, cmdline) to the log would be good. And not automatically truncate the log when big but just append or roll it. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
