summaryrefslogtreecommitdiff
path: root/doc/reference
diff options
context:
space:
mode:
authorXavier Morel <xmo@odoo.com>2018-05-14 13:57:27 +0000
committerXavier Morel <xmo@odoo.com>2018-11-27 14:05:03 +0000
commit92d5a4bce5a3878e10427ec8dfef8c4b21f64f3d (patch)
tree0b8550445223ad5d814c9fe878b7fb9991e72cca /doc/reference
parentcb7589aaa5902c56ae5cbb9cee7b81b6b21bacb7 (diff)
[REM] builtin logrotate features
It's completely FUBAR when using workers[0] and properly reimplementing it is not really worth the effort when logrotate(8) and newsyslog(8) exist (or cyclog/multilog/cronolog if you subscribe to the "logrotate and newsyslog are a design that should be consigned to history" school of thought). [0] https://stackoverflow.com/questions/34186774/why-doesnt-timedrotatingfilehandler-work-properly-and-how-to-solve-this-issuer closes odoo/odoo#29073
Diffstat (limited to 'doc/reference')
-rw-r--r--doc/reference/cmdline.rst13
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/reference/cmdline.rst b/doc/reference/cmdline.rst
index 83df644f150..de96e733959 100644
--- a/doc/reference/cmdline.rst
+++ b/doc/reference/cmdline.rst
@@ -304,19 +304,6 @@ customize the amount of logging output
<https://docs.python.org/2/library/logging.handlers.html#watchedfilehandler>`_
and will automatically be reopened when replaced
-.. option:: --logrotate
-
- enables `log rotation <https://docs.python.org/2/library/logging.handlers.html#timedrotatingfilehandler>`_
- daily, keeping 30 backups. Log rotation frequency and number of backups is
- not configurable.
-
- .. danger::
-
- Built-in log rotation is not reliable in multi-workers scenarios
- and may incur significant data loss. It is *strongly recommended* to
- use an external log rotation utility or use system loggers (--syslog)
- instead.
-
.. option:: --syslog
logs to the system's event logger: `syslog on unices <https://docs.python.org/2/library/logging.handlers.html#sysloghandler>`_