aboutsummaryrefslogtreecommitdiff
path: root/src/daemon/command_server.cpp (follow)
AgeCommit message (Collapse)AuthorFilesLines
2019-03-17Merge pull request #5185Riccardo Spagni1-0/+5
59478c80 daemon: new mining_status command (moneromooo-monero)
2019-03-09daemon: new mining_status commandmoneromooo-monero1-0/+5
2019-03-05Update 2019 copyrightbinaryFate1-1/+1
2019-02-23miner: it can now autodetect the optimal number of threadsmoneromooo-monero1-2/+2
2019-01-28Merge pull request #5080Riccardo Spagni1-0/+1
d294a577 daemon: extend 'print_pl' command, optional filter by type and limit (xiphon)
2019-01-22Pruningmoneromooo-monero1-0/+10
The blockchain prunes seven eighths of prunable tx data. This saves about two thirds of the blockchain size, while keeping the node useful as a sync source for an eighth of the blockchain. No other data is currently pruned. There are three ways to prune a blockchain: - run monerod with --prune-blockchain - run "prune_blockchain" in the monerod console - run the monero-blockchain-prune utility The first two will prune in place. Due to how LMDB works, this will not reduce the blockchain size on disk. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. The third way will create a second database, a pruned copy of the original one. Since this is a new file, this one will be smaller than the original one. Once the database is pruned, it will stay pruned as it syncs. That is, there is no need to use --prune-blockchain again, etc.
2019-01-18daemon: extend 'print_pl' command, optional filter by type and limitxiphon1-0/+1
2018-11-28add command pop_blocksJason Wong1-0/+6
add new public method to Blockchain and update according to code review update after review: better lock/unlock, try catch and coding style
2018-06-26alt_chain_info can now give more info about a particular alt chainmoneromooo-monero1-0/+1
2018-04-13daemon: add a version commandmoneromooo-monero1-0/+5
2018-01-29Allow the number of incoming connections to be limitedErik de Castro Lopo1-0/+6
It was already possible to limit outgoing connections. One might want to do this on home network connections with high bandwidth but low usage caps.
2018-01-26Update 2018 copyrightxmr-eric1-1/+1
2017-12-16move includes around to lessen overall loadmoneromooo-monero1-0/+2
2017-11-26Added command descriptionsCifrado1-47/+89
2017-10-08Fix #2559: more flexible print_tx daemon commandbinaryFate1-1/+1
2017-09-22Log categories can now be added to and removed frommoneromooo-monero1-1/+1
Also, set_log without parameters now prints the log categories
2017-09-08updated clarification bc_dyn_stats Matthew Campassi1-1/+1
updated clarification of required parameter for bc_dyn_stats
2017-09-08clarification bc_dyn_statsMatthew Campassi1-1/+1
clarification of required parameter for bc_dyn_stats
2017-08-18clarification of parameters for print_coinbase_tx_sumMatthew Campassi1-1/+1
2017-08-07cryptonote_protocol_handler: sync speedupmoneromooo-monero1-0/+5
A block queue is now placed between block download and block processing. Blocks are now requested only from one peer (unless starved). Includes a new sync_info coommand.
2017-05-19Fix typoxmr-eric1-1/+1
2017-04-02daemon: new relay_tx command and RPCmoneromooo-monero1-0/+5
2017-02-24daemon/rpc: updates command and RPCmoneromooo-monero1-0/+5
subcommands "check", "download", and "update". update is not yet implemented.
2017-02-23Add print_pl_stats daemon commandMiguel Herranz1-0/+5
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni1-1/+1
2017-02-16More robust battery status handling.Dion Ahmetaj1-1/+1
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.
2017-02-10Background/smart mining. If a users' computer is plugged into a powerDion Ahmetaj1-1/+1
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).
2017-02-06Add server auth to monerod, and client auth to wallet-cli and wallet-rpcLee Clagett1-2/+2
2017-01-16Change logging to easylogging++moneromooo-monero1-1/+4
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.
2017-01-13rpc: add a command to get info about the current blockchainmoneromooo-monero1-0/+5
About the tip of the main chain, and the last N blocks
2016-12-17rpc: new function and RPC to get alternative chain infomoneromooo-monero1-0/+5
2016-10-23daemon: add a print_pool_stats daemon commandmoneromooo-monero1-0/+5
Helps see what's going on now that Monero is getting used
2016-10-10changed params from start/end index to height/countDion Ahmetaj1-1/+1
2016-10-10attempted to remove whitespace spamDion Ahmetaj1-6/+6
2016-10-10added print_coinbase_tx_sum optionDion Ahmetaj1-6/+11
2016-10-03Removed all code related to fast_exitNanoAkron1-5/+0
2016-09-18epee: optionally restrict HTTP service to a configurable user agentmoneromooo-monero1-1/+2
This is intended to catch traffic coming from a web browser, so we avoid issues with a web page sending a transfer RPC to the wallet. Requiring a particular user agent can act as a simple password scheme, while we wait for 0MQ and proper authentication to be merged.
2016-08-30Fix incorrect help usage for the threads option to start_miningQuanah Gibson-Mount1-1/+1
2016-03-26New RPC and daemon command to get output histogrammoneromooo-monero1-0/+5
This is a list of existing output amounts along with the number of outputs of that amount in the blockchain. The daemon command takes: - no parameters: all outputs with at least 3 instances - one parameter: all outputs with at least that many instances - two parameters: all outputs within that many instances The default starts at 3 to avoid massive spamming of all dust outputs in the blockchain, and is the current minimum mixin requirement. An optional vector of amounts may be passed, to request histogram only for those outputs.
2016-03-21Revert "Print stack trace upon exceptions"moneromooo-monero1-1/+0
Ain't nobody got time for link/cmake skullduggery. This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
2016-03-19Print stack trace upon exceptionsmoneromooo-monero1-0/+1
Useful for debugging users' logs
2016-01-30new flush_txpool command, and associated RPC callmoneromooo-monero1-0/+5
It can flush a particular tx, or the whole pool (the RPC command can flush a list of transactions too)
2016-01-14'max limit of...' is redundant wording, rephrasebinaryFate1-1/+1
2015-12-31update versionRiccardo Spagni1-1/+1
2015-12-31updated copyright yearRiccardo Spagni1-1/+1
2015-11-26add RPC calls and commands to get/set bansmoneromooo-monero1-0/+15
2015-10-25daemon: add a status commandmoneromooo-monero1-0/+5
Displays current block height and target, net hash, hard fork basic info, and connections. Useful as a basic user friendly "what's going on here" command.
2015-09-19Add an RPC call and daemon command to get info on hard fork votingmoneromooo-monero1-0/+5
2015-08-11Add a is_key_image_spent daemon command and RPC callmoneromooo-monero1-0/+5
2015-06-03fix ^D exit for bitmonerodmoneromooo-monero1-2/+2
It uses the async console handler differently than simplewallet, and wasn't running the same exit code, causing it to never actually exit after breaking out of the console entry loop.
2015-05-31cleaning up, removing redundant files, renaming, fixing incorrect licensesRiccardo Spagni1-7/+7
2015-04-01remerged; commands JSON. logging upgrade. doxygenrfree2monero1-2/+22
2015-03-27Restore daemon interactive modeThomas Winget1-1/+30
Daemon interactive mode is now working again. RPC mapped calls in daemon and wallet have both had connection_context removed as an argument as that argument was not being used anywhere.
2015-02-24RPC calls for background daemon added inThomas Winget1-1/+6
The RPC calls the daemon executable uses to talk to the running daemon instance have mostly been added back in. Rate limiting has not been added in upstream, but is on its way in a separate effort, so those calls are still NOPed out.
2015-02-24Daemonize changes pulled in -- daemon buildsThomas Winget1-0/+179
many RPC functions added by the daemonize changes (and related changes on the upstream dev branch that were not merged) were commented out (apart from return). Other than that, this *should* work...at any rate, it builds, and that's something.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 19:15:57 +0000