Launching from command line
A batch/shell file can be created to launch nanominer with command line arguments. This file must call the cmdline_launcher script (cmdline_launcher.bat on Windows, cmdline_launcher.sh on Linux), which converts the command line into a config called config_cmdline.ini and launches the miner with it. At least one algorithm and wallet must be passed to the cmdline_launcher script. All common config parameters in the command line must be specified before the first "algo" parameter. Here are some examples of command lines for launching Ethereum and PascalCoin:
Windows
cmdline_launcher -algo ethash -wallet YOUR_ETH_WALLET -coin eth -rigName YOUR_ETH_WORKER -email YOUR_EMAIL -algo randomhash -wallet YOUR_PASC_WALLET -coin pasc -rigName YOUR_PASC_WORKER -email YOUR_EMAIL
Linux
./cmdline_launcher.sh -algo ethash -wallet YOUR_ETH_WALLET -coin eth -rigName YOUR_ETH_WORKER -email YOUR_EMAIL -algo randomhash -wallet YOUR_PASC_WALLET -coin pasc -rigName YOUR_PASC_WORKER -email YOUR_EMAIL
Log Files
The event log function on nanominer is automatically activated each time the program starts up. The log files that are created contain all the information displayed on the console while the miner is running. By default, the log files are saved in the logs folder of the program's current directory. Deactivating event logging, as well as assigning a random catalogue for recording log files, can be done by using the corresponding configuration parameters (see the examples in the Parameters section of this file).
noLog |
Optional common parameter. This parameter accepts the values true or false (the default is false). If this parameter is set to true then no log files will be recorded onto the hard drive.
|
noColor |
Optional common parameter. This parameter accepts the values true or false (the default is false). If this parameter is set to true then the console output won't contain any colors.
|
logPath |
Optional common parameter. This parameter can either be used to set the name of the folder in which log files will be created logfolder, or to specify a path to single file, which will be used for all logs. Both relative and absolute paths work. Default value for this parameter is logs folder in the main miner folder.
Examples:logPath=logfolder
logPath=logs/log.txt
logPath=/var/log/nanominer/log.txt
logPath=C:\logs\log.txt |
Automatic Restart Function
With default settings, nanominer will automatically restart if it encounters critical errors in the GPU or lag. (These errors usually arise due to hardware problems or overclocking the GPU.) The automatic restart function can be deactivated using the watchdog parameter.
Likewise, the minHashrate (minimum hashrate) parameter allows the user to set the value of the minimum hashrate which, if exceeded, will cause the miner to restart. This function uses the average hashrate over the last ten minutes, as displayed in blue in the console log. If the average hashrate over 10 minutes is lower than the set value, the miner will restart. With default settings the minimum hashrate is not set.
Another function on nanominer that improves the miner's automatic functioning is handled by the restarts parameter.It sets the number of times the miner restarts before rebooting the worker (rig). By default the miner will only restart itself.
minHashrate |
Optional algorithm parameter. This is the minimum acceptable hashrate. This function keeps track of the rig's total hashrate and compares it with this parameter. If five minutes after the miner is launched the set minimum is not reached, nanominer will automatically restart. Likewise, the miner will restart if for any reason the average hashrate over a ten-minute period falls below the set value. This value can be set with an optional modifier letter that represents a thousand for kilohash or a million for megahash per second. For example, setting the value to 100 megahashes per second can be written as 100M, 100.0M, 100m, 100000k, 100000K or 100000000. If this parameter is not defined, the miner will not restart (with the exception of the situations described in the watchdog section).
|
restarts |
Optional common parameter. This parameter sets the number of times the miner will restart before rebooting the rig. In case of GPU problems like hardware errors or lag, or in case of hashrate degradation (if the minhashrate option is used), nanominer will restart. However, certain errors cannot be fixed by restarting the program. In such cases it is necessary to reboot the rig.
|
watchdog |
Optional common parameter. This parameter manages the miner's restart function when running into critical GPU errors or lag. It accepts the values true or false. By default, true – automatic restart - is activated. |
To reboot, the miner loads the reboot.bat script from the current directory if running on Windows or reboot.sh if on Linux:
rebootThe reboot.sh file on Linux must be given execute permissions in order for it to work. The typical content of the reboot.bat script for Windows:
shutdown /r /t 5 /fThe script must be written by the user. To run reboot script instead of restarting miner every time a critical error occurs, just set
restarts=0
Auto-update options
checkForUpdates |
Optional common parameter. This parameter accepts the values true or false (the default is true). If this parameter is set to false then nanominer stops checking for the newest release version on every startup. |
autoUpdate |
Optional common parameter. This parameter accepts the values true or false (the default is false). If this parameter is set to true and checking for updates is enabled, then nanominer will update itself on every startup, provided there is a newer version available. |
Pool options
sortPools |
Optional algorithm parameter. This parameter accepts the values true or false (the default is false). If this parameter is set to true then the best pool will be chosen by least ping (not by the pool list). |
sendHashrate |
Optional algorithm parameter for Ethash and Ubqhash algorithms. This parameter accepts the values true or false. The default value is true (if JSON-RPC pool protocol is used). |
farmRecheck |
Optional algorithm parameter. The interval (in milliseconds) between polling the node for new jobs in solo mining mode for QuarkChain. Default value is 200. |
shardId |
Optional algorithm parameter. Can be used to set a shard ID for QuarkChain solo mining. Only shards using Ethash algorithm are supported. This parameter should be specified in hex, e.g. 0x1, 0x10001, 0x10002, etc. For more information on shards, visit this and this link. Default shard ID is 0x1. |
ETH tools
epoch |
Optional algorithm parameter. Ethash algorithm specific option to check miner behaviour on different Ethash epochs. |