Topic: bitcoind 17mb? How to shrink it after compiling? (Read 1256 times)
the database format itself is compatible, the transaction logs are not. remove /database/log.* while bitcoind is stopped and you can happily switch from bdb5.1 back to 4.6 and similar stunts.
Update:
It would appear that the unstripped version is not production safe. It damaged the database and now when i try to run normal (non-compiled) client, it crashes with following error:
EDIT:
Actually, I can only run compiled versions now, the binary version from bitcoin.org crashes every time i try to launch it using the same database. Any ideas ?
Perhaps different version of BerkeleyDB on my debian system or whatever ?
It would appear that the unstripped version is not production safe. It damaged the database and now when i try to run normal (non-compiled) client, it crashes with following error:
Quote
************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in AppInit()
terminate called after throwing an instance of 'DbRunRecoveryException'
what(): DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in AppInit()
terminate called after throwing an instance of 'DbRunRecoveryException'
what(): DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
EDIT:
Actually, I can only run compiled versions now, the binary version from bitcoin.org crashes every time i try to launch it using the same database. Any ideas ?
Perhaps different version of BerkeleyDB on my debian system or whatever ?
I would recommend not stripping it unless you have some specific need to. The larger size is due to debug information that is never loaded or used when the program is running (it doesn't actually bloat memory or slow execution in any way). But without it, you cannot make sense of core dumps.
I have just compiled it and it is also 17 MB...
So you are saying this is completely normal, and i have absolutely nothing to worry about, including running that version on production servers ?
I would recommend not stripping it unless you have some specific need to. The larger size is due to debug information that is never loaded or used when the program is running (it doesn't actually bloat memory or slow execution in any way). But without it, you cannot make sense of core dumps.
thank you! duh.
what util would one use to strip it down to the size that normally gets released?
Simply "strip bitcoin"!
Maybe you compiled it with debug code?
after compiling bitcoind it's come out as 17mb... it actually runs fine (finally, yay!), but I'm wondering what is the final step in the process... what util would one use to strip it down to the size that normally gets released?
Jump to: