From a32ffd18314d4ba71af687b4583152aa19822f6f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Piotr=20W=C5=82odarek?= Date: Wed, 31 Oct 2018 21:23:56 +0100 Subject: [PATCH] Add --max-log-file-size=0 explanation thanks to @gingeropolous --- docs/interacting/monero-config-file.md | 2 +- docs/interacting/monerod-reference.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/interacting/monero-config-file.md b/docs/interacting/monero-config-file.md index 2be82c7..29898bf 100644 --- a/docs/interacting/monero-config-file.md +++ b/docs/interacting/monero-config-file.md @@ -49,7 +49,7 @@ translates to: # Log file log-file=/var/log/monero/monero.log - max-log-file-size=1073741824 # Set to 1GB to mitigate log trimming by monerod; we prefer logrotate + max-log-file-size=0 # Prevent monerod from managing the log files; we want logrotate to take care of that # P2P full node p2p-bind-ip=0.0.0.0 # Bind to all interfaces (the default) diff --git a/docs/interacting/monerod-reference.md b/docs/interacting/monerod-reference.md index c349184..2084f5c 100644 --- a/docs/interacting/monerod-reference.md +++ b/docs/interacting/monerod-reference.md @@ -80,7 +80,7 @@ The following groups are only to make reference easier to follow. The daemon its |-----------------------|---------------------------------------------------------------------------------------------------------------------------------------- | `--log-file` | Full path to the log file. Example (mind file permissions):
`./monerod --log-file=/var/log/monero/mainnet/monerod.log` | `--log-level` | `0-4` with `0` being minimal logging and `4` being full tracing. Defaults to `0`. These are general presets and do not directly map to severity levels. For example, even with minimal `0`, you may see some most important `INFO` entries. Temporarily changing to `1` allows for much better understanding of how the full node operates. Example:
`./monerod --log-level=1` -| `--max-log-file-size` | Soft limit in bytes for the log file (=104850000 by default, which is just under 100MB). Once log file grows past that limit, `monerod` creates next log file with a `-YYYY-MM-DD-HH-MM-SS` UTC timestamp postfix. In production deployments, you would probably prefer to use established solutions like logrotate instead. +| `--max-log-file-size` | Soft limit in bytes for the log file (=104850000 by default, which is just under 100MB). Once log file grows past that limit, `monerod` creates the next log file with a UTC timestamp postfix `-YYYY-MM-DD-HH-MM-SS`.

In production deployments, you would probably prefer to use established solutions like logrotate instead. In that case, set `--max-log-file-size=0` to prevent monerod from managing the log files. | `--max-log-files` | 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. #### Server