installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.
- On MacOS X 10.5 and later systems, you can create libraries and
+ On macOS 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple `-arch' options to the
compiler but only a single `-arch' option to the preprocessor. Like
found_pam_lib=no
AC_CHECK_LIB(pam, pam_start, [found_pam_lib=yes], [], [$lt_cv_dlopen_libs])
#
- # Some PAM implementations (MacOS X for example) put the PAM headers
+ # Some PAM implementations (macOS for example) put the PAM headers
# in /usr/include/pam instead of /usr/include/security...
#
found_pam_hdrs=no
support the automatic restarting of system calls.
Unfortunately, not all operating systems do this by
default, and even those that do may have bugs. For
- example, Mac OS X fails to restart the t\btc\bcg\bge\bet\bta\bat\btt\btr\br() and
- t\btc\bcs\bse\bet\bta\bat\btt\btr\br() system calls (this is a bug in Mac OS X).
+ example, macOS fails to restart the t\btc\bcg\bge\bet\bta\bat\btt\btr\br() and
+ t\btc\bcs\bse\bet\bta\bat\btt\btr\br() system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the
command stopping with the SIGTTIN or SIGTTOU signals,
programs that catch these signals and suspend
file distributed with s\bsu\bud\bdo\bo or https://www.sudo.ws/license.html for
complete details.
-Sudo 1.8.20 February 16, 2017 Sudo 1.8.20
+Sudo 1.8.21 June 2, 2017 Sudo 1.8.21
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.TH "SUDO_PLUGIN" "5" "February 16, 2017" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
+.TH "SUDO_PLUGIN" "5" "June 2, 2017" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
.nh
.if n .ad l
.SH "NAME"
automatic restarting of system calls.
Unfortunately, not all operating systems do this by default,
and even those that do may have bugs.
-For example, Mac OS X fails to restart the
+For example, macOS fails to restart the
\fBtcgetattr\fR()
and
\fBtcsetattr\fR()
-system calls (this is a bug in Mac OS X).
+system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the command stopping with the
\fRSIGTTIN\fR
or
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.Dd February 16, 2017
+.Dd June 2, 2017
.Dt SUDO_PLUGIN @mansectform@
.Os Sudo @PACKAGE_VERSION@
.Sh NAME
automatic restarting of system calls.
Unfortunately, not all operating systems do this by default,
and even those that do may have bugs.
-For example, Mac OS X fails to restart the
+For example, macOS fails to restart the
.Fn tcgetattr
and
.Fn tcsetattr
-system calls (this is a bug in Mac OS X).
+system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the command stopping with the
.Dv SIGTTIN
or
support the automatic restarting of system calls.
Unfortunately, not all operating systems do this by
default, and even those that do may have bugs. For
- example, Mac OS X fails to restart the t\btc\bcg\bge\bet\bta\bat\btt\btr\br() and
- t\btc\bcs\bse\bet\bta\bat\btt\btr\br() system calls (this is a bug in Mac OS X).
+ example, macOS fails to restart the t\btc\bcg\bge\bet\bta\bat\btt\btr\br() and
+ t\btc\bcs\bse\bet\bta\bat\btt\btr\br() system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the
command stopping with the SIGTTIN or SIGTTOU signals,
programs that catch these signals and suspend
a command may only be run after the audit event is
successfully written. This flag is only effective on
systems for which s\bsu\bud\bdo\boe\ber\brs\bs supports audit logging,
- including FreeBSD, Linux, Mac OS X and Solaris. This
- flag is _\bo_\bn by default.
+ including FreeBSD, Linux, macOS and Solaris. This flag
+ is _\bo_\bn by default.
ignore_dot If set, s\bsu\bud\bdo\bo will ignore "." or "" (both denoting
current directory) in the PATH environment variable;
affected.
The _\bn_\bo_\be_\bx_\be_\bc feature is known to work on SunOS, Solaris, *BSD,
- Linux, IRIX, Tru64 UNIX, MacOS X, HP-UX 11.x and AIX 5.3 and
+ Linux, IRIX, Tru64 UNIX, macOS, HP-UX 11.x and AIX 5.3 and
above. It should be supported on most operating systems that
support the LD_PRELOAD environment variable. Check your
operating system's manual pages for the dynamic linker (usually
file distributed with s\bsu\bud\bdo\bo or https://www.sudo.ws/license.html for
complete details.
-Sudo 1.8.20 May 10, 2017 Sudo 1.8.20
+Sudo 1.8.21 June 2, 2017 Sudo 1.8.21
.\" Agency (DARPA) and Air Force Research Laboratory, Air Force
.\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
.\"
-.TH "SUDOERS" "5" "May 10, 2017" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
+.TH "SUDOERS" "5" "June 2, 2017" "Sudo @PACKAGE_VERSION@" "File Formats Manual"
.nh
.if n .ad l
.SH "NAME"
automatic restarting of system calls.
Unfortunately, not all operating systems do this by default,
and even those that do may have bugs.
-For example, Mac OS X fails to restart the
+For example, macOS fails to restart the
\fBtcgetattr\fR()
and
\fBtcsetattr\fR()
-system calls (this is a bug in Mac OS X).
+system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the command stopping with the
\fRSIGTTIN\fR
or
written.
This flag is only effective on systems for which
\fBsudoers\fR
-supports audit logging, including FreeBSD, Linux, Mac OS X and Solaris.
+supports audit logging, including FreeBSD, Linux, macOS and Solaris.
This flag is
\fIon\fR
by default.
The
\fInoexec\fR
feature is known to work on SunOS, Solaris, *BSD,
-Linux, IRIX, Tru64 UNIX, MacOS X, HP-UX 11.x and AIX 5.3 and above.
+Linux, IRIX, Tru64 UNIX, macOS, HP-UX 11.x and AIX 5.3 and above.
It should be supported on most operating systems that support the
\fRLD_PRELOAD\fR
environment variable.
.\" Agency (DARPA) and Air Force Research Laboratory, Air Force
.\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
.\"
-.Dd May 10, 2017
+.Dd June 2, 2017
.Dt SUDOERS @mansectform@
.Os Sudo @PACKAGE_VERSION@
.Sh NAME
automatic restarting of system calls.
Unfortunately, not all operating systems do this by default,
and even those that do may have bugs.
-For example, Mac OS X fails to restart the
+For example, macOS fails to restart the
.Fn tcgetattr
and
.Fn tcsetattr
-system calls (this is a bug in Mac OS X).
+system calls (this is a bug in macOS).
Furthermore, because this behavior depends on the command stopping with the
.Dv SIGTTIN
or
written.
This flag is only effective on systems for which
.Nm
-supports audit logging, including FreeBSD, Linux, Mac OS X and Solaris.
+supports audit logging, including FreeBSD, Linux, macOS and Solaris.
This flag is
.Em on
by default.
The
.Em noexec
feature is known to work on SunOS, Solaris, *BSD,
-Linux, IRIX, Tru64 UNIX, MacOS X, HP-UX 11.x and AIX 5.3 and above.
+Linux, IRIX, Tru64 UNIX, macOS, HP-UX 11.x and AIX 5.3 and above.
It should be supported on most operating systems that support the
.Ev LD_PRELOAD
environment variable.
NJOBS=0
case "`uname`" in
Darwin)
- # Mac OS X
+ # macOS
NJOBS=`sysctl -n hw.ncpu`
;;
Linux)
%endif
%if [macos]
- # System Integrity Protection on Mac OS X won't allow us to write
+ # System Integrity Protection on macOS won't allow us to write
# directly to /etc or /var. We must install in /private instead.
case "$sudoersdir" in
/etc|/etc/*)