| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| | |
0288310e blockchain_db: add "raw" blobdata getters for block and transaction (moneromooo-monero)
|
| | |
| |
| |
| | |
This speeds up operations such as serving blocks to syncing peers
|
| |\ \
| | |
| | |
| | | |
69ab14d9 More robust battery status handling. (Dion Ahmetaj)
|
| | |/
| |
| |
| |
| |
| | |
Added an extra path to check for linux power supply status.
Added ignore battery option. If set to true, then when we can't figure out
the power status, we'll assume the system is plugged in.
|
| |/ |
|
| |\
| |
| |
| |
| |
| | |
3b6839cc mlog: move log level changes to global level (moneromooo-monero)
38a1b9c9 rpc: fix daemon mixed style set_log 2,category:level (moneromooo-monero)
28d0b11f mlog: s/Mew/New/ in log (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| | |
was resetting bg mining enabled instead of started. Upped the miner threshold. Also moved setting of enabled on start above miner thread creation since starting with true, then stopping, then starting with false resulted in race condition.
|
| |/
|
|
|
|
|
|
|
|
|
| |
source, and CPU has been idle for some time, then begin mining to some
threshold (don't destroy the users' CPU).
This patch only supports windows and linux (I've only tested on Win64 and
Ubuntu).
The variables currently default to pretty conservative values (i.e. 20%
CPU mining threshold).
|
| |\
| |
| |
| | |
ce7fcbb4 Add server auth to monerod, and client auth to wallet-cli and wallet-rpc (Lee Clagett)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
cc1462e0 Add concurrency check to rpc mining to ensure not too many threads. number of cores times 4 or 257. (Ashley Perpetual)
|
| | |
| |
| |
| | |
of cores times 4 or 257.
|
| |\ \
| | |
| | |
| | | |
99f58437 Fix invalid + of std::string and int (Timothy D. Prime)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These warnings were emitted by clang++, and they are real bugs.
src/rpc/core_rpc_server.cpp:208:58: warning: adding 'uint64_t'
(aka 'unsigned long') to a string does not append to the string
[-Wstring-plus-int]
res.status = "Error retrieving block at height " + height;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
The obvious intent is achieved by using std::to_string().
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
b70ab128 rpc: fix orphan_status when getting blocks (moneromooo-monero)
|
| | |
| |
| |
| | |
It was always set to false, even for orphan blocks
|
| |/
|
|
|
| |
This prevents easy fingerprinting when you change IPs, and
will be a must when kovri gets used.
|
| |\
| |
| |
| | |
16b8b66a specify restore height by YYYY-MM-DD format (kenshi84)
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the epee and data_loggers logging systems with
a single one, and also adds filename:line and explicit severity
levels. Categories may be defined, and logging severity set
by category (or set of categories). epee style 0-4 log level
maps to a sensible severity configuration. Log files now also
rotate when reaching 100 MB.
To select which logs to output, use the MONERO_LOGS environment
variable, with a comma separated list of categories (globs are
supported), with their requested severity level after a colon.
If a log matches more than one such setting, the last one in
the configuration string applies. A few examples:
This one is (mostly) silent, only outputting fatal errors:
MONERO_LOGS=*:FATAL
This one is very verbose:
MONERO_LOGS=*:TRACE
This one is totally silent (logwise):
MONERO_LOGS=""
This one outputs all errors and warnings, except for the
"verify" category, which prints just fatal errors (the verify
category is used for logs about incoming transactions and
blocks, and it is expected that some/many will fail to verify,
hence we don't want the spam):
MONERO_LOGS=*:WARNING,verify:FATAL
Log levels are, in decreasing order of priority:
FATAL, ERROR, WARNING, INFO, DEBUG, TRACE
Subcategories may be added using prefixes and globs. This
example will output net.p2p logs at the TRACE level, but all
other net* logs only at INFO:
MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE
Logs which are intended for the user (which Monero was using
a lot through epee, but really isn't a nice way to go things)
should use the "global" category. There are a few helper macros
for using this category, eg: MGINFO("this shows up by default")
or MGINFO_RED("this is red"), to try to keep a similar look
and feel for now.
Existing epee log macros still exist, and map to the new log
levels, but since they're used as a "user facing" UI element
as much as a logging system, they often don't map well to log
severities (ie, a log level 0 log may be an error, or may be
something we want the user to see, such as an important info).
In those cases, I tried to use the new macros. In other cases,
I left the existing macros in. When modifying logs, it is
probably best to switch to the new macros with explicit levels.
The --log-level options and set_log commands now also accept
category settings, in addition to the epee style log levels.
|
| | |
|
| |\
| |
| |
| | |
81c384e4 fix do_not_relay not preventing relaying on a timer (moneromooo-monero)
|
| | |
| |
| |
| | |
Also print its value when printing pool
|
| |/
|
|
| |
About the tip of the main chain, and the last N blocks
|
| |\
| |
| |
| | |
19be7225 Add start_time to get_info methods and show uptime (Miguel Herranz)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| | |
1607cb7e tx_pool: better block template filling algorithm (moneromooo-monero)
9731b4e5 rpc: add block size to GET_BLOCK_HEADER RPC (moneromooo-monero)
9188b346 rpc: add current block size to the getinfo call (moneromooo-monero)
|
| | |
| |
| |
| | |
and print it in print_bc
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Daemon RPC version is now composed of a major and minor number,
so that incompatible changes bump the major version, while
compatible changes can still bump the minor version without
causing clients to unnecessarily complain.
|
| |
|
|
|
|
| |
Those aren't yet in the blockchain, so will not be found
(and aren't yet known, since it depends on where exactly the
tx will be mined in the next block or blocks)
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Someone apparently needs that to make a wallet but never asked.
If you read that and that's not what you wanted, the bugtracker
is at https://github.com/monero-project/monero/issues
|
| |
|
|
|
|
|
|
|
| |
I forgot to bump it previously when changing RPC, most notably
for the addition of the unlocked field in the histogram RPC.
This causes new wallets to not realize when they're talking to
an older daemon, and get confused trying to get outputs to use
as fake outs. This otherwise gratuitous bump ensures than old
daemons will be detected by wallets using this code.
|
| | |
|
| |\
| |
| |
| |
| |
| | |
10a79ea daemon: report transaction relay status in print_pool* commands (moneromooo-monero)
1e16366 core: notify the txpool when transactions are relayed (moneromooo-monero)
f3c374f tx_pool: set relayed flag on relay (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
5e10fb0 rpc: add blockchain cumulative difficulty to getinfo call (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
094f4c8 rpc: add missing top block hash to json getinfo call (moneromooo-monero)
|