Browse Source

Fix log message

master
Neil Booth 8 years ago
parent
commit
0f43ce564a
  1. 15
      docs/ENVIRONMENT.rst
  2. 2
      server/block_processor.py

15
docs/ENVIRONMENT.rst

@ -65,11 +65,12 @@ These environment variables are optional:
* **DB_ENGINE** * **DB_ENGINE**
Database engine for the transaction database. The default is Database engine for the UTXO and history database. The default is
`leveldb`. Supported alternatives are `rocksdb` and `lmdb`. You `leveldb`. Supported alternatives are `rocksdb` and `lmdb`. You
will need to install the appropriate python package for your engine. will need to install the appropriate python package for your engine.
The value is not case sensitive. Note that the current way The value is not case sensitive. Note that the current way
ElectrumX uses LMDB gives poor performance . ElectrumX uses LMDB results in poor performance. I intend to improve
this.
* **REORG_LIMIT** * **REORG_LIMIT**
@ -96,8 +97,8 @@ These environment variables are optional:
* **RPC_PORT** * **RPC_PORT**
ElectrumX will listen on this port for local RPC connections. ElectrumX will listen on this port for local RPC connections.
ElectrumX listens for RPC connections unless this is explicity set ElectrumX listens for RPC connections unless this is explicitly set
to blank. It defaults appropriately for **COIN** and **NETWORK** to blank. The default is appropriate for **COIN** and **NETWORK**
(e.g., 8000 for Bitcoin mainnet) if not set. (e.g., 8000 for Bitcoin mainnet) if not set.
* **DONATION_ADDRESS** * **DONATION_ADDRESS**
@ -107,9 +108,9 @@ These environment variables are optional:
* **BANNER_FILE** * **BANNER_FILE**
The path to a banner file to serve to clients. Relative file paths The path to a banner file to serve to clients in Electrum's
must be relative to **DB_DIRECTORY**. The banner file is re-read "Console" tab. Relative file paths must be relative to
for each new client. **DB_DIRECTORY**. The banner file is re-read for each new client.
You can place several meta-variables in your banner file, which will be You can place several meta-variables in your banner file, which will be
replaced before serving to a client. replaced before serving to a client.

2
server/block_processor.py

@ -62,7 +62,7 @@ class Prefetcher(LoggedClass):
else: else:
self.refill_event.set() self.refill_event.set()
self.fetched_height = height self.fetched_height = height
self.logger.info('reset to height'.format(height)) self.logger.info('reset to height {:,d}'.format(height))
async def get_blocks(self): async def get_blocks(self):
'''Return the next list of blocks from our prefetch cache. '''Return the next list of blocks from our prefetch cache.

Loading…
Cancel
Save