syslog_badpri to the "Strings at can be used in a boolean context" section.
password before s\bsu\bud\bdo\bo logs the failure and exits. The
default is 3.
+ syslog_maxlen On many systems, syslog(3) has a relatively small log
+ buffer. IETF RFC 5424 states that syslog servers must
+ support messages of at least 480 bytes and should
+ support messages up to 2048 bytes. By default, s\bsu\bud\bdo\boe\ber\brs\bs
+ creates log messages up to 980 bytes which corresponds
+ to the historic BSD syslog implementation which used a
+ 1024 byte buffer to store the message, date, hostname
+ and program name. To prevent syslog messages from
+ being truncated, s\bsu\bud\bdo\boe\ber\brs\bs will split up log messages
+ that are larger than _\bs_\by_\bs_\bl_\bo_\bg_\b__\bm_\ba_\bx_\bl_\be_\bn bytes. When a
+ message is split, additional parts will include the
+ string "(command continued)" after the user name and
+ before the continued command line arguments.
+
+ This setting is only supported by version 1.8.19 or
+ higher.
+
I\bIn\bnt\bte\beg\bge\ber\brs\bs t\bth\bha\bat\bt c\bca\ban\bn b\bbe\be u\bus\bse\bed\bd i\bin\bn a\ba b\bbo\boo\bol\ble\bea\ban\bn c\bco\bon\bnt\bte\bex\bxt\bt:
loglinelen Number of characters per line for the file log. This
not specified on the command line. This defaults to
root.
- syslog_badpri Syslog priority to use when the user is not allowed to
- run a command or when authentication is unsuccessful.
- Defaults to alert.
-
- The following syslog priorities are supported: a\bal\ble\ber\brt\bt,
- c\bcr\bri\bit\bt, d\bde\beb\bbu\bug\bg, e\bem\bme\ber\brg\bg, e\ber\brr\br, i\bin\bnf\bfo\bo, n\bno\bot\bti\bic\bce\be, w\bwa\bar\brn\bni\bin\bng\bg, and
- n\bno\bon\bne\be. Negating the option or setting it to a value of
- n\bno\bon\bne\be will disable logging of unsuccessful commands.
-
- syslog_goodpri Syslog priority to use when the user is allowed to run
- a command and authentication is successful. Defaults
- to notice.
-
- See _\bs_\by_\bs_\bl_\bo_\bg_\b__\bb_\ba_\bd_\bp_\br_\bi for the list of supported syslog
- priorities. Negating the option or setting it to a
- value of n\bno\bon\bne\be will disable logging of successful
- commands.
-
- syslog_maxlen On many systems, syslog(3) has a relatively small log
- buffer. IETF RFC 5424 states that syslog servers must
- support messages of at least 480 bytes and should
- support messages up to 2048 bytes. By default, s\bsu\bud\bdo\boe\ber\brs\bs
- creates log messages up to 980 bytes which corresponds
- to the historic BSD syslog implementation which used a
- 1024 byte buffer to store the message, date, hostname
- and program name. To prevent syslog messages from
- being truncated, s\bsu\bud\bdo\boe\ber\brs\bs will split up log messages
- that are larger than _\bs_\by_\bs_\bl_\bo_\bg_\b__\bm_\ba_\bx_\bl_\be_\bn bytes. When a
- message is split, additional parts will include the
- string "(command continued)" after the user name and
- before the continued command line arguments.
-
- This setting is only supported by version 1.8.19 or
- higher.
-
sudoers_locale Locale to use when parsing the sudoers file, logging
commands, and sending email. Note that changing the
locale may affect how sudoers is interpreted. Defaults
your OS supports it), a\bau\but\bth\bh, d\bda\bae\bem\bmo\bon\bn, u\bus\bse\ber\br, l\blo\boc\bca\bal\bl0\b0, l\blo\boc\bca\bal\bl1\b1,
l\blo\boc\bca\bal\bl2\b2, l\blo\boc\bca\bal\bl3\b3, l\blo\boc\bca\bal\bl4\b4, l\blo\boc\bca\bal\bl5\b5, l\blo\boc\bca\bal\bl6\b6, and l\blo\boc\bca\bal\bl7\b7.
+ syslog_badpri
+ Syslog priority to use when the user is not allowed to run
+ a command or when authentication is unsuccessful. Defaults
+ to alert.
+
+ The following syslog priorities are supported: a\bal\ble\ber\brt\bt, c\bcr\bri\bit\bt,
+ d\bde\beb\bbu\bug\bg, e\bem\bme\ber\brg\bg, e\ber\brr\br, i\bin\bnf\bfo\bo, n\bno\bot\bti\bic\bce\be, w\bwa\bar\brn\bni\bin\bng\bg, and n\bno\bon\bne\be.
+ Negating the option or setting it to a value of n\bno\bon\bne\be will
+ disable logging of unsuccessful commands.
+
+ syslog_goodpri
+ Syslog priority to use when the user is allowed to run a
+ command and authentication is successful. Defaults to
+ notice.
+
+ See _\bs_\by_\bs_\bl_\bo_\bg_\b__\bb_\ba_\bd_\bp_\br_\bi for the list of supported syslog
+ priorities. Negating the option or setting it to a value
+ of n\bno\bon\bne\be will disable logging of successful commands.
+
verifypw This option controls when a password will be required when
a user runs s\bsu\bud\bdo\bo with the -\b-v\bv option. It has the following
possible values:
logs the failure and exits.
The default is
\fR@passwd_tries@\fR.
+.TP 18n
+syslog_maxlen
+On many systems,
+syslog(3)
+has a relatively small log buffer.
+IETF RFC 5424 states that syslog servers must support messages of
+at least 480 bytes and should support messages up to 2048 bytes.
+By default,
+\fBsudoers\fR
+creates log messages up to 980 bytes which corresponds to the
+historic BSD syslog implementation which used a 1024 byte buffer
+to store the message, date, hostname and program name.
+To prevent syslog messages from being truncated,
+\fBsudoers\fR
+will split up log messages that are larger than
+\fIsyslog_maxlen\fR
+bytes.
+When a message is split, additional parts will include the string
+\(Lq(command continued)\(Rq
+after the user name and before the continued command line arguments.
+.sp
+This setting is only supported by version 1.8.19 or higher.
.PP
\fBIntegers that can be used in a boolean context\fR:
.TP 18n
This defaults to
\fR@runas_default@\fR.
.TP 18n
-syslog_badpri
-Syslog priority to use when the user is not allowed to run a command or
-when authentication is unsuccessful.
-Defaults to
-\fR@badpri@\fR.
-.sp
-The following syslog priorities are supported:
-\fBalert\fR,
-\fBcrit\fR,
-\fBdebug\fR,
-\fBemerg\fR,
-\fBerr\fR,
-\fBinfo\fR,
-\fBnotice\fR,
-\fBwarning\fR,
-and
-\fBnone\fR.
-Negating the option or setting it to a value of
-\fBnone\fR
-will disable logging of unsuccessful commands.
-.TP 18n
-syslog_goodpri
-Syslog priority to use when the user is allowed to run a command and
-authentication is successful.
-Defaults to
-\fR@goodpri@\fR.
-.sp
-See
-\fIsyslog_badpri\fR
-for the list of supported syslog priorities.
-Negating the option or setting it to a value of
-\fBnone\fR
-will disable logging of successful commands.
-.TP 18n
-syslog_maxlen
-On many systems,
-syslog(3)
-has a relatively small log buffer.
-IETF RFC 5424 states that syslog servers must support messages of
-at least 480 bytes and should support messages up to 2048 bytes.
-By default,
-\fBsudoers\fR
-creates log messages up to 980 bytes which corresponds to the
-historic BSD syslog implementation which used a 1024 byte buffer
-to store the message, date, hostname and program name.
-To prevent syslog messages from being truncated,
-\fBsudoers\fR
-will split up log messages that are larger than
-\fIsyslog_maxlen\fR
-bytes.
-When a message is split, additional parts will include the string
-\(Lq(command continued)\(Rq
-after the user name and before the continued command line arguments.
-.sp
-This setting is only supported by version 1.8.19 or higher.
-.TP 18n
sudoers_locale
Locale to use when parsing the sudoers file, logging commands, and
sending email.
and
\fBlocal7\fR.
.TP 14n
+syslog_badpri
+.br
+Syslog priority to use when the user is not allowed to run a command or
+when authentication is unsuccessful.
+Defaults to
+\fR@badpri@\fR.
+.sp
+The following syslog priorities are supported:
+\fBalert\fR,
+\fBcrit\fR,
+\fBdebug\fR,
+\fBemerg\fR,
+\fBerr\fR,
+\fBinfo\fR,
+\fBnotice\fR,
+\fBwarning\fR,
+and
+\fBnone\fR.
+Negating the option or setting it to a value of
+\fBnone\fR
+will disable logging of unsuccessful commands.
+.TP 14n
+syslog_goodpri
+Syslog priority to use when the user is allowed to run a command and
+authentication is successful.
+Defaults to
+\fR@goodpri@\fR.
+.sp
+See
+\fIsyslog_badpri\fR
+for the list of supported syslog priorities.
+Negating the option or setting it to a value of
+\fBnone\fR
+will disable logging of successful commands.
+.TP 14n
verifypw
This option controls when a password will be required when a user runs
\fBsudo\fR
logs the failure and exits.
The default is
.Li @passwd_tries@ .
+.It syslog_maxlen
+On many systems,
+.Xr syslog 3
+has a relatively small log buffer.
+IETF RFC 5424 states that syslog servers must support messages of
+at least 480 bytes and should support messages up to 2048 bytes.
+By default,
+.Nm
+creates log messages up to 980 bytes which corresponds to the
+historic BSD syslog implementation which used a 1024 byte buffer
+to store the message, date, hostname and program name.
+To prevent syslog messages from being truncated,
+.Nm
+will split up log messages that are larger than
+.Em syslog_maxlen
+bytes.
+When a message is split, additional parts will include the string
+.Dq Pq command continued
+after the user name and before the continued command line arguments.
+.Pp
+This setting is only supported by version 1.8.19 or higher.
.El
.Pp
.Sy Integers that can be used in a boolean context :
option is not specified on the command line.
This defaults to
.Li @runas_default@ .
-.It syslog_badpri
-Syslog priority to use when the user is not allowed to run a command or
-when authentication is unsuccessful.
-Defaults to
-.Li @badpri@ .
-.Pp
-The following syslog priorities are supported:
-.Sy alert ,
-.Sy crit ,
-.Sy debug ,
-.Sy emerg ,
-.Sy err ,
-.Sy info ,
-.Sy notice ,
-.Sy warning ,
-and
-.Sy none .
-Negating the option or setting it to a value of
-.Sy none
-will disable logging of unsuccessful commands.
-.It syslog_goodpri
-Syslog priority to use when the user is allowed to run a command and
-authentication is successful.
-Defaults to
-.Li @goodpri@ .
-.Pp
-See
-.Em syslog_badpri
-for the list of supported syslog priorities.
-Negating the option or setting it to a value of
-.Sy none
-will disable logging of successful commands.
-.It syslog_maxlen
-On many systems,
-.Xr syslog 3
-has a relatively small log buffer.
-IETF RFC 5424 states that syslog servers must support messages of
-at least 480 bytes and should support messages up to 2048 bytes.
-By default,
-.Nm
-creates log messages up to 980 bytes which corresponds to the
-historic BSD syslog implementation which used a 1024 byte buffer
-to store the message, date, hostname and program name.
-To prevent syslog messages from being truncated,
-.Nm
-will split up log messages that are larger than
-.Em syslog_maxlen
-bytes.
-When a message is split, additional parts will include the string
-.Dq Pq command continued
-after the user name and before the continued command line arguments.
-.Pp
-This setting is only supported by version 1.8.19 or higher.
.It sudoers_locale
Locale to use when parsing the sudoers file, logging commands, and
sending email.
.Sy local6 ,
and
.Sy local7 .
+.It syslog_badpri
+Syslog priority to use when the user is not allowed to run a command or
+when authentication is unsuccessful.
+Defaults to
+.Li @badpri@ .
+.Pp
+The following syslog priorities are supported:
+.Sy alert ,
+.Sy crit ,
+.Sy debug ,
+.Sy emerg ,
+.Sy err ,
+.Sy info ,
+.Sy notice ,
+.Sy warning ,
+and
+.Sy none .
+Negating the option or setting it to a value of
+.Sy none
+will disable logging of unsuccessful commands.
+.It syslog_goodpri
+Syslog priority to use when the user is allowed to run a command and
+authentication is successful.
+Defaults to
+.Li @goodpri@ .
+.Pp
+See
+.Em syslog_badpri
+for the list of supported syslog priorities.
+Negating the option or setting it to a value of
+.Sy none
+will disable logging of successful commands.
.It verifypw
This option controls when a password will be required when a user runs
.Nm sudo
projects / sudo / commitdiff