Subversion Repositories configs

Rev

Rev 192 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
192 - 1
# Configuration file for NetworkManager.
2
#
3
# See "man 5 NetworkManager.conf" for details.
4
#
5
# The directories /usr/lib/NetworkManager/conf.d/ and /run/NetworkManager/conf.d/
203 - 6
# can contain additional .conf snippets installed by packages. These files are
192 - 7
# read before NetworkManager.conf and have thus lowest priority.
203 - 8
# The directory /etc/NetworkManager/conf.d/ can contain additional .conf
192 - 9
# snippets. Those snippets are merged last and overwrite the settings from this main
10
# file.
11
#
12
# The files within one conf.d/ directory are read in asciibetical order.
13
#
203 - 14
# You can prevent loading a file /usr/lib/NetworkManager/conf.d/NAME.conf
15
# by having a file NAME.conf in either /run/NetworkManager/conf.d/ or /etc/NetworkManager/conf.d/.
16
# Likewise, snippets from /run can be prevented from loading by placing
17
# a file with the same name in /etc/NetworkManager/conf.d/.
192 - 18
#
19
# If two files define the same key, the one that is read afterwards will overwrite
20
# the previous one.
21
 
22
[main]
23
#plugins=ifcfg-rh
24
 
25
 
26
[logging]
27
# When debugging NetworkManager, enabling debug logging is of great help.
28
#
29
# Logfiles contain no passwords and little sensitive information. But please
30
# check before posting the file online. You can also personally hand over the
203 - 31
# logfile to a NM developer to treat it confidential. Meet us on #nm on Libera.Chat.
192 - 32
#
33
# You can also change the log-level at runtime via
34
#   $ nmcli general logging level TRACE domains ALL
35
# However, usually it's cleaner to enable debug logging
36
# in the configuration and restart NetworkManager so that
37
# debug logging is enabled from the start.
38
#
39
# You will find the logfiles in syslog, for example via
40
#   $ journalctl -u NetworkManager
41
#
203 - 42
# Please post full logfiles for bug reports without pre-filtering or truncation.
43
# Also, for debugging the entire `journalctl` output can be interesting. Don't
44
# limit unnecessarily with `journalctl -u`. Exceptions are if you are worried
45
# about private data. Check before posting logfiles!
46
#
192 - 47
# Note that debug logging of NetworkManager can be quite verbose. Some messages
48
# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
203 - 49
# in man journald.conf). Please disable rate-limiting before collecting debug logs!
192 - 50
#
51
#level=TRACE
52
#domains=ALL