Mercurial > prosody-modules
annotate misc/upstart/prosody.conf @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | 68b56506fa50 |
children |
rev | line source |
---|---|
2610 | 1 author "Kim Alvefur <zash@zash.se>" |
2 description "Prosody XMPP server" | |
3 | |
4 # Normal runlevel based start and stop | |
5 start on runlevel [2345] | |
6 stop on runlevel [!2345] | |
7 | |
8 # Alternate method for starting and stopping | |
9 # when a network interface comes and goes | |
10 # | |
11 # start on net-device-up IFACE=eth0 | |
12 # stop on net-device-down IFACE=eth0 | |
13 | |
14 # Change user so Prosdy doesn't have to | |
15 setgid prosody | |
16 setuid prosody | |
17 | |
18 # Set a sensible umask | |
19 umask 0027 | |
20 | |
21 # Run prosody | |
22 exec /usr/bin/prosody | |
23 | |
24 # Collect stdout into a log file | |
25 console log | |
26 | |
27 # Restart on crashes | |
28 respawn | |
29 respawn limit 5 10 |