aboutsummaryrefslogtreecommitdiffstats
path: root/man2
diff options
context:
space:
mode:
Diffstat (limited to 'man2')
-rw-r--r--man2/bind.22
-rw-r--r--man2/chmod.22
-rw-r--r--man2/chown.22
-rw-r--r--man2/chroot.22
-rw-r--r--man2/getpriority.24
-rw-r--r--man2/idle.22
-rw-r--r--man2/reboot.22
-rw-r--r--man2/setgid.22
-rw-r--r--man2/setresuid.22
-rw-r--r--man2/setup.22
10 files changed, 11 insertions, 11 deletions
diff --git a/man2/bind.2 b/man2/bind.2
index 6502e971d4..741fb5d711 100644
--- a/man2/bind.2
+++ b/man2/bind.2
@@ -126,7 +126,7 @@ is set appropriately.
.SH ERRORS
.TP
.B EACCES
-The address is protected, and the user is not the super-user.
+The address is protected, and the user is not the superuser.
.TP
.B EBADF
.I sockfd
diff --git a/man2/chmod.2 b/man2/chmod.2
index 2886a6e1a4..85b5a9f9c6 100644
--- a/man2/chmod.2
+++ b/man2/chmod.2
@@ -108,7 +108,7 @@ may be turned off if a file is written.
(On Linux this occurs if the writing process does not have the
.B CAP_FSETID
capability.)
-On some file systems, only the super-user can set the sticky bit,
+On some file systems, only the superuser can set the sticky bit,
which may have a special meaning.
For the sticky bit, and for set user ID and set group ID bits on
directories, see
diff --git a/man2/chown.2 b/man2/chown.2
index 2e4ebca7b8..3e0fc3c0e5 100644
--- a/man2/chown.2
+++ b/man2/chown.2
@@ -63,7 +63,7 @@ or
.I group
is specified as \-1, then that ID is not changed.
-When the owner or group of an executable file are changed by a non-super-user,
+When the owner or group of an executable file are changed by a non-superuser,
the S_ISUID and S_ISGID mode bits are cleared. POSIX does not specify whether
this also should happen when root does the
.IR chown ;
diff --git a/man2/chroot.2 b/man2/chroot.2
index 44be6ce2a0..3232e10739 100644
--- a/man2/chroot.2
+++ b/man2/chroot.2
@@ -54,7 +54,7 @@ and does nothing else.
This call does not change the current working directory,
so that after the call `.' can be outside the tree rooted at `/'.
-In particular, the super-user can escape from a `chroot jail'
+In particular, the superuser can escape from a `chroot jail'
by doing `mkdir foo; chroot foo; cd ..'.
This call does not close open file descriptors, and such file
diff --git a/man2/getpriority.2 b/man2/getpriority.2
index 39960f6810..b3a3c563a3 100644
--- a/man2/getpriority.2
+++ b/man2/getpriority.2
@@ -96,7 +96,7 @@ call returns the highest priority (lowest numerical value)
enjoyed by any of the specified processes. The
.B setpriority
call sets the priorities of all of the specified processes
-to the specified value. Only the super-user may lower priorities.
+to the specified value. Only the superuser may lower priorities.
.SH "RETURN VALUE"
Since
.B getpriority
@@ -139,7 +139,7 @@ and (on Linux systems) the caller did not have the
capability.
.TP
.B EACCES
-A non super-user attempted to lower a process priority.
+A non superuser attempted to lower a process priority.
.SH NOTES
The details on the condition for EPERM depend on the system.
The above description is what SUSv3 says, and seems to be followed on
diff --git a/man2/idle.2 b/man2/idle.2
index 35d13c26cd..a54f0869ed 100644
--- a/man2/idle.2
+++ b/man2/idle.2
@@ -46,7 +46,7 @@ never returns.
.PP
Only process 0 may call
.BR idle .
-Any user process, even a process with super-user permission,
+Any user process, even a process with superuser permission,
will receive
.BR EPERM .
.SH "RETURN VALUE"
diff --git a/man2/reboot.2 b/man2/reboot.2
index af90fb7414..cbc5b074dd 100644
--- a/man2/reboot.2
+++ b/man2/reboot.2
@@ -115,7 +115,7 @@ This means that the CAD keystroke will cause a SIGINT signal to be
sent to init (process 1), whereupon this process may decide upon a
proper action (maybe: kill all processes, sync, reboot).
.LP
-Only the super-user may use this function.
+Only the superuser may use this function.
.LP
The precise effect of the above actions depends on the architecture.
For the i386 architecture, the additional argument does not do
diff --git a/man2/setgid.2 b/man2/setgid.2
index a2cdcad8f8..dfcc9bc460 100644
--- a/man2/setgid.2
+++ b/man2/setgid.2
@@ -51,7 +51,7 @@ is set appropriately.
.SH ERRORS
.TP
.B EPERM
-The user is not the super-user (does not have the CAP_SETGID capability), and
+The user is not the superuser (does not have the CAP_SETGID capability), and
.I gid
does not match the effective group ID or saved set-group-ID of
the calling process.
diff --git a/man2/setresuid.2 b/man2/setresuid.2
index c4e9d6f850..e51b938d5d 100644
--- a/man2/setresuid.2
+++ b/man2/setresuid.2
@@ -44,7 +44,7 @@ real, effective and saved user ID nonzero) may change the real,
effective and saved user ID, each to one of:
the current uid, the current effective uid or the current saved uid.
-The super-user may set real, effective and saved user ID to arbitrary values.
+The superuser may set real, effective and saved user ID to arbitrary values.
If one of the parameters equals \-1, the corresponding value is not changed.
diff --git a/man2/setup.2 b/man2/setup.2
index 12578ae460..d3ae830024 100644
--- a/man2/setup.2
+++ b/man2/setup.2
@@ -49,7 +49,7 @@ configured into the kernel and then mounts the root file system.
.PP
No user process may call
.BR setup .
-Any user process, even a process with super-user permission,
+Any user process, even a process with superuser permission,
will receive
.BR EPERM .
.SH "RETURN VALUE"