]> git.proxmox.com Git - mirror_ovs.git/blame - lib/vlog-unixctl.man
ofp-ed-props: Fix using uninitialized padding for NSH encap actions.
[mirror_ovs.git] / lib / vlog-unixctl.man
CommitLineData
b16fdafe
BP
1.SS "VLOG COMMANDS"
2These commands manage \fB\*(PN\fR's logging settings.
2a3e30b2
BP
3.IP "\fBvlog/set\fR [\fIspec\fR]"
4Sets logging levels. Without any \fIspec\fR, sets the log level for
d5460484 5every module and destination to \fBdbg\fR. Otherwise, \fIspec\fR is a
2a3e30b2
BP
6list of words separated by spaces or commas or colons, up to one from
7each category below:
b16fdafe
BP
8.
9.RS
10.IP \(bu
2a3e30b2
BP
11A valid module name, as displayed by the \fBvlog/list\fR command on
12\fBovs\-appctl\fR(8), limits the log level change to the specified
13module.
b16fdafe
BP
14.
15.IP \(bu
2a3e30b2
BP
16\fBsyslog\fR, \fBconsole\fR, or \fBfile\fR, to limit the log level
17change to only to the system log, to the console, or to a file,
18respectively.
5a6af13f
GS
19.IP
20On Windows platform, \fBsyslog\fR is accepted as a word and is only
21useful along with the \fB\-\-syslog\-target\fR option (the word has no
22effect otherwise).
2a3e30b2 23.
b16fdafe 24.IP \(bu
2a3e30b2
BP
25\fBoff\fR, \fBemer\fR, \fBerr\fR, \fBwarn\fR, \fBinfo\fR, or
26\fBdbg\fR, to control the log level. Messages of the given severity
27or higher will be logged, and messages of lower severity will be
28filtered out. \fBoff\fR filters out all messages. See
29\fBovs\-appctl\fR(8) for a definition of each log level.
30.RE
31.
32.IP
33Case is not significant within \fIspec\fR.
34.IP
35Regardless of the log levels set for \fBfile\fR, logging to a file
36will not take place unless \fB\*(PN\fR was invoked with the
37\fB\-\-log\-file\fR option.
38.IP
39For compatibility with older versions of OVS, \fBany\fR is accepted as
40a word but has no effect.
b16fdafe 41.RE
d5460484
GS
42.IP "\fBvlog/set PATTERN:\fIdestination\fB:\fIpattern\fR"
43Sets the log pattern for \fIdestination\fR to \fIpattern\fR. Refer to
3fbe1d30 44\fBovs\-appctl\fR(8) for a description of the valid syntax for \fIpattern\fR.
b16fdafe
BP
45.
46.IP "\fBvlog/list\fR"
47Lists the supported logging modules and their current levels.
48.
532e1463
AA
49.IP "\fBvlog/list-pattern\fR"
50Lists logging patterns used for each destination.
51.
06380128
BP
52.IP "\fBvlog/close\fR"
53Causes \fB\*(PN\fR to close its log file, if it is open. (Use
54\fBvlog/reopen\fR to reopen it later.)
55.
b16fdafe 56.IP "\fBvlog/reopen\fR"
06380128
BP
57Causes \fB\*(PN\fR to close its log file, if it is open, and then
58reopen it. (This is useful after rotating log files, to cause a new
59log file to be used.)
b16fdafe
BP
60.IP
61This has no effect unless \fB\*(PN\fR was invoked with the
4e312e69 62\fB\-\-log\-file\fR option.
93161ce9
BP
63.
64.IP "\fBvlog/disable\-rate\-limit \fR[\fImodule\fR]..."
65.IQ "\fBvlog/enable\-rate\-limit \fR[\fImodule\fR]..."
66By default, \fB\*(PN\fR limits the rate at which certain messages can
67be logged. When a message would appear more frequently than the
68limit, it is suppressed. This saves disk space, makes logs easier to
69read, and speeds up execution, but occasionally troubleshooting
70requires more detail. Therefore, \fBvlog/disable\-rate\-limit\fR
71allows rate limits to be disabled at the level of an individual log
72module. Specify one or more module names, as displayed by the
73\fBvlog/list\fR command. Specifying either no module names at all or
74the keyword \fBany\fR disables rate limits for every log module.
75.
76.IP
77The \fBvlog/enable\-rate\-limit\fR command, whose syntax is the same
78as \fBvlog/disable\-rate\-limit\fR, can be used to re-enable a rate
79limit that was previously disabled.