</code></pre></div><p>The <ahref=/infrastructure/networks>mainnnet</a> is when you want to deal with the real XMR.</p><divclass=highlight><pre><span></span><code>./monerod --detach # run as a daemon in background
</code></pre></div><h2id=options>Options<aclass=headerlinkhref=#optionstitle="Permanent link">¶</a></h2><p>Options define how the daemon should be working. Their names follow the <code>--option-name</code> pattern.</p><p>The following groups are only to make reference easier to follow. The daemon itself does not group options in any way.</p><h4id=help-and-version>Help and version<aclass=headerlinkhref=#help-and-versiontitle="Permanent link">¶</a></h4><table><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td><code>--help</code></td><td>Enlist available options.</td></tr><tr><td><code>--version</code></td><td>Show <code>monerod</code> version to stdout. Example output: <br><code>Monero 'Oxygen Orion' (v0.17.1.8-release)</code></td></tr><tr><td><code>--os-version</code></td><td>Show build timestamp and target operating system. Example output:<br><code>OS: Linux #65-Ubuntu SMP Thu Dec 10 12:01:51 UTC 2020 5.4.0-59-generic</code>.</td></tr><tr><td><code>--check-updates</code></td><td>One of: <code>disabled</code> | <code>notify</code> | <code>download</code> (=<code>notify</code> by default). Check for new versions of Monero and optionally download it. You should probably prefer your OS package manager to do the update, if possible. There is also unimplemented <code>update</code> option shown by the help system.</td></tr></tbody></table><h4id=pick-network>Pick network<aclass=headerlinkhref=#pick-networktitle="Permanent link">¶</a></h4><table><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>(missing)</td><td>By default monerod assumes <ahref=/infrastructure/networks>mainnet</a>.</td></tr><tr><td><code>--stagenet</code></td><td>Run on <ahref=/infrastructure/networks>stagenet</a>. Remember to run your wallet with <code>--stagenet</code> as well.</td></tr><tr><td><code>--testnet</code></td><td>Run on <ahref=/infrastructure/networks>testnet</a>. Remember to run your wallet with <code>--testnet</code> as well.</td></tr></tbody></table><h4id=logging>Logging<aclass=headerlinkhref=#loggingtitle="Permanent link">¶</a></h4><table><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td><code>--log-file</code></td><td>Full path to the log file. Example (mind file permissions): <br><code>./monerod --log-file=/var/log/monero/mainnet/monerod.log</code></td></tr><tr><td><code>--log-level</code></td><td><code>0-4</code> with <code>0</code> being minimal logging and <code>4</code> being full tracing. Defaults to <code>0</code>. These are general presets and do not directly map to severity levels. For example, even with minimal <code>0</code>, you may see some most important <code>INFO</code> entries. Temporarily changing to <code>1</code> allows for much better understanding of how the full node operates. Example: <br><code>./monerod --log-level=1</code></td></tr><tr><td><code>--max-log-file-size</code></td><td>Soft limit in bytes for the log file (=104850000 by default, which is just under 100MB). Once log file grows past that limit, <code>monerod</code> creates the next log file with a UTC timestamp postfix <code>-YYYY-MM-DD-HH-MM-SS</code>.<br><br>In production deployments, you would probably prefer to use established solutions like logrotate instead. In that case, set <code>--max-log-file-size=0</code> to prevent monerod from managing the log files.</td></tr><tr><td><code>--max-log-files</code></td><td>Limit on the number of log files (=50 by default). The oldest log files are removed. In production deployments, you would probably prefer to use established solutions like logrotate instead.</td></tr></tbody></table><h4id=server>Server<aclass=headerlinkhref=#servertitle="Permanent link">¶</a></h4><p><code>monerod</code> defaults are adjusted for running it occasionally on the same computer as your Monero wallet.</p><p>The following options will be helpful if you intend to have an always running node — most likely on a remote server or your ow
