mirror of
https://github.com/element-hq/synapse
synced 2024-08-19 02:10:55 +00:00
deploy: 2069231645
This commit is contained in:
parent
a3255f90e2
commit
fee779b5c5
4 changed files with 10 additions and 8 deletions
|
@ -7059,9 +7059,10 @@ trusted_key_servers:
|
||||||
</code></pre>
|
</code></pre>
|
||||||
<div style="break-before: page; page-break-before: always;"></div><h1 id="logging-sample-configuration-file"><a class="header" href="#logging-sample-configuration-file">Logging Sample Configuration File</a></h1>
|
<div style="break-before: page; page-break-before: always;"></div><h1 id="logging-sample-configuration-file"><a class="header" href="#logging-sample-configuration-file">Logging Sample Configuration File</a></h1>
|
||||||
<p>Below is a sample logging configuration file. This file can be tweaked to control how your
|
<p>Below is a sample logging configuration file. This file can be tweaked to control how your
|
||||||
homeserver will output logs. A restart of the server is generally required to apply any
|
homeserver will output logs. The value of the <code>log_config</code> option in your homeserver config
|
||||||
changes made to this file. The value of the <code>log_config</code> option in your homeserver
|
should be the path to this file.</p>
|
||||||
config should be the path to this file.</p>
|
<p>To apply changes made to this file, send Synapse a SIGHUP signal (or, if using <code>systemd</code>, run
|
||||||
|
<code>systemctl reload</code> on the Synapse service).</p>
|
||||||
<p>Note that a default logging configuration (shown below) is created automatically alongside
|
<p>Note that a default logging configuration (shown below) is created automatically alongside
|
||||||
the homeserver config when following the <a href="usage/configuration/../../setup/installation.html">installation instructions</a>.
|
the homeserver config when following the <a href="usage/configuration/../../setup/installation.html">installation instructions</a>.
|
||||||
It should be named <code><SERVERNAME>.log.config</code> by default.</p>
|
It should be named <code><SERVERNAME>.log.config</code> by default.</p>
|
||||||
|
|
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
|
@ -148,9 +148,10 @@
|
||||||
|
|
||||||
<h1 id="logging-sample-configuration-file"><a class="header" href="#logging-sample-configuration-file">Logging Sample Configuration File</a></h1>
|
<h1 id="logging-sample-configuration-file"><a class="header" href="#logging-sample-configuration-file">Logging Sample Configuration File</a></h1>
|
||||||
<p>Below is a sample logging configuration file. This file can be tweaked to control how your
|
<p>Below is a sample logging configuration file. This file can be tweaked to control how your
|
||||||
homeserver will output logs. A restart of the server is generally required to apply any
|
homeserver will output logs. The value of the <code>log_config</code> option in your homeserver config
|
||||||
changes made to this file. The value of the <code>log_config</code> option in your homeserver
|
should be the path to this file.</p>
|
||||||
config should be the path to this file.</p>
|
<p>To apply changes made to this file, send Synapse a SIGHUP signal (or, if using <code>systemd</code>, run
|
||||||
|
<code>systemctl reload</code> on the Synapse service).</p>
|
||||||
<p>Note that a default logging configuration (shown below) is created automatically alongside
|
<p>Note that a default logging configuration (shown below) is created automatically alongside
|
||||||
the homeserver config when following the <a href="../../setup/installation.html">installation instructions</a>.
|
the homeserver config when following the <a href="../../setup/installation.html">installation instructions</a>.
|
||||||
It should be named <code><SERVERNAME>.log.config</code> by default.</p>
|
It should be named <code><SERVERNAME>.log.config</code> by default.</p>
|
||||||
|
|
Loading…
Reference in a new issue