aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2017-10-20 16:55:10 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2017-10-20 16:55:10 +0200
commit26cd31fd4acafbf68a17d420f3946683792f9be8 (patch)
tree06090ed3a756c9fedf4a603f3ffae1352fcc7bb0
parentcdcc4450a0f72de4e00e4867817defe91b5c088b (diff)
downloadman-pages-26cd31fd4acafbf68a17d420f3946683792f9be8.tar.gz
access.2, delete_module.2, eventfd.2, fallocate.2, fcntl.2, getrandom.2, init_module.2, open.2, seccomp.2, timerfd_create.2, openpty.3, pthread_spin_lock.3, shm_open.3, tempnam.3, fifo.7, keyrings.7, pid_namespaces.7, sched.7, thread-keyring.7: wfix (will fail --> fail/fails)
Reported-by: Pedro Alves <palves@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/access.22
-rw-r--r--man2/delete_module.22
-rw-r--r--man2/eventfd.24
-rw-r--r--man2/fallocate.24
-rw-r--r--man2/fcntl.22
-rw-r--r--man2/getrandom.22
-rw-r--r--man2/init_module.22
-rw-r--r--man2/open.23
-rw-r--r--man2/seccomp.22
-rw-r--r--man2/timerfd_create.24
-rw-r--r--man3/openpty.36
-rw-r--r--man3/pthread_spin_lock.32
-rw-r--r--man3/shm_open.32
-rw-r--r--man3/tempnam.32
-rw-r--r--man7/fifo.76
-rw-r--r--man7/keyrings.72
-rw-r--r--man7/pid_namespaces.74
-rw-r--r--man7/sched.72
-rw-r--r--man7/thread-keyring.72
19 files changed, 28 insertions, 27 deletions
diff --git a/man2/access.2 b/man2/access.2
index 952604ad1f..2778c8e2c3 100644
--- a/man2/access.2
+++ b/man2/access.2
@@ -319,7 +319,7 @@ directories in the path prefix of
grant search (i.e., execute) access.
If any directory is inaccessible, then the
.BR access ()
-call will fail, regardless of the permissions on the file itself.
+call fails, regardless of the permissions on the file itself.
.PP
Only access bits are checked, not the file type or contents.
Therefore, if a directory is found to be writable,
diff --git a/man2/delete_module.2 b/man2/delete_module.2
index a38432bcea..daa15faa25 100644
--- a/man2/delete_module.2
+++ b/man2/delete_module.2
@@ -106,7 +106,7 @@ By default, if a module has an
.I init
function but no
.I exit
-function, then an attempt to remove the module will fail.
+function, then an attempt to remove the module fails.
However, if
.BR O_TRUNC
was specified, this requirement is bypassed.
diff --git a/man2/eventfd.2 b/man2/eventfd.2
index c63891a07f..4c9001ed71 100644
--- a/man2/eventfd.2
+++ b/man2/eventfd.2
@@ -80,7 +80,7 @@ Each successful
returns an 8-byte integer.
A
.BR read (2)
-will fail with the error
+fails with the error
.B EINVAL
if the size of the supplied buffer is less than 8 bytes.
.IP
@@ -141,7 +141,7 @@ if the file descriptor has been made nonblocking.
.IP
A
.BR write (2)
-will fail with the error
+fails with the error
.B EINVAL
if the size of the supplied buffer is less than 8 bytes,
or if an attempt is made to write the value 0xffffffffffffffff.
diff --git a/man2/fallocate.2 b/man2/fallocate.2
index d3d310dee3..461b2be2b6 100644
--- a/man2/fallocate.2
+++ b/man2/fallocate.2
@@ -165,7 +165,7 @@ must be a multiple of the filesystem logical block size,
which varies according to the filesystem type and configuration.
If a filesystem has such a requirement,
.BR fallocate ()
-will fail with the error
+fails with the error
.BR EINVAL
if this requirement is violated.
.PP
@@ -267,7 +267,7 @@ This mode has the same limitations as
regarding the granularity of the operation.
If the granularity requirements are not met,
.BR fallocate ()
-will fail with the error
+fails with the error
.BR EINVAL.
If the
.I offset
diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 722c251a9d..6764238415 100644
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -1417,7 +1417,7 @@ If this seal is set, any further call to
.BR fcntl ()
with
.B F_ADD_SEALS
-will fail with
+fails with the error
.BR EPERM .
Therefore, this seal prevents any modifications to the set of seals itself.
If the initial set of seals of a file includes
diff --git a/man2/getrandom.2 b/man2/getrandom.2
index da49e5d875..f8377cbc4e 100644
--- a/man2/getrandom.2
+++ b/man2/getrandom.2
@@ -246,7 +246,7 @@ source is interrupted by a signal handler
depends on the initialization state of the entropy buffer
and on the request size,
.IR buflen .
-If the entropy is not yet initialized, then the call will fail with the
+If the entropy is not yet initialized, then the call fails with the
.B EINTR
error.
If the entropy pool has been initialized
diff --git a/man2/init_module.2 b/man2/init_module.2
index 8e095bb006..4f13edf1fe 100644
--- a/man2/init_module.2
+++ b/man2/init_module.2
@@ -148,7 +148,7 @@ flag indicates that the "vermagic" string is to be ignored, and the
flag indicates that the symbol version hashes are to be ignored.
If the kernel is built to permit forced loading (i.e., configured with
.BR CONFIG_MODULE_FORCE_LOAD ),
-then loading will continue, otherwise it will fail with
+then loading continues, otherwise it fails with the error
.B ENOEXEC
as expected for malformed modules.
.SH RETURN VALUE
diff --git a/man2/open.2 b/man2/open.2
index c44e987fc8..02a62a2558 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -429,7 +429,8 @@ and
.I pathname
already exists, then
.BR open ()
-will fail.
+fails with the error
+.BR EEXIST .
.IP
When these two flags are specified, symbolic links are not followed:
.\" POSIX.1-2001 explicitly requires this behavior.
diff --git a/man2/seccomp.2 b/man2/seccomp.2
index 6b851c4794..a99c262596 100644
--- a/man2/seccomp.2
+++ b/man2/seccomp.2
@@ -148,7 +148,7 @@ the thread must make the following call:
.IP
Otherwise, the
.BR SECCOMP_SET_MODE_FILTER
-operation will fail and return
+operation fails and returns
.BR EACCES
in
.IR errno .
diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2
index 0401a68f19..31ee21f315 100644
--- a/man2/timerfd_create.2
+++ b/man2/timerfd_create.2
@@ -297,7 +297,7 @@ flag).
.IP
A
.BR read (2)
-will fail with the error
+fails with the error
.B EINVAL
if the size of the supplied buffer is less than 8 bytes.
.IP
@@ -313,7 +313,7 @@ was specified when calling
.BR timerfd_settime (),
then
.BR read (2)
-will fail with the error
+fails with the error
.BR ECANCELED
if the real-time clock undergoes a discontinuous change.
(This allows the reading application to discover
diff --git a/man3/openpty.3 b/man3/openpty.3
index c35a74bcbb..56c8b4411c 100644
--- a/man3/openpty.3
+++ b/man3/openpty.3
@@ -130,20 +130,20 @@ return 0, and the parent process of
returns the process ID of the child process.
.SH ERRORS
.BR openpty ()
-will fail if:
+fails if:
.TP
.B ENOENT
There are no available terminals.
.PP
.BR login_tty ()
-will fail if
+fails if
.BR ioctl (2)
fails to set
.I fd
to the controlling terminal of the calling process.
.PP
.BR forkpty ()
-will fail if either
+fails if either
.BR openpty ()
or
.BR fork (2)
diff --git a/man3/pthread_spin_lock.3 b/man3/pthread_spin_lock.3
index 887cb5be25..df69451f30 100644
--- a/man3/pthread_spin_lock.3
+++ b/man3/pthread_spin_lock.3
@@ -100,7 +100,7 @@ may fail with the following errors:
The system detected a deadlock condition.
.PP
.BR pthread_spin_trylock ()
-will fail with the following errors:
+fails with the following errors:
.TP
.B EBUSY
The spin lock is currently locked by another thread.
diff --git a/man3/shm_open.3 b/man3/shm_open.3
index 4e01b4ac93..95bc7cb458 100644
--- a/man3/shm_open.3
+++ b/man3/shm_open.3
@@ -165,7 +165,7 @@ attempts to
.BR shm_open ()
an object with the same
.I name
-will fail (unless
+fail (unless
.B O_CREAT
was specified, in which case a new, distinct object is created).
.SH RETURN VALUE
diff --git a/man3/tempnam.3 b/man3/tempnam.3
index 5ccb09b547..51ccfef462 100644
--- a/man3/tempnam.3
+++ b/man3/tempnam.3
@@ -174,7 +174,7 @@ uses at most the first five bytes from
.PP
The glibc implementation of
.BR tempnam ()
-will fail with the error
+fails with the error
.B EEXIST
upon failure to find a unique name.
.SH BUGS
diff --git a/man7/fifo.7 b/man7/fifo.7
index d7dde7ca58..aa73f9dd69 100644
--- a/man7/fifo.7
+++ b/man7/fifo.7
@@ -34,9 +34,9 @@ until the other end is opened also.
.PP
A process can open a FIFO in nonblocking mode.
In this
-case, opening for read-only will succeed even if no-one has
-opened on the write side yet and opening for write-only will
-fail with
+case, opening for read-only succeeds even if no-one has
+opened on the write side yet and opening for write-only
+fails with
.B ENXIO
(no such device or address) unless the other
end has already been opened.
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 3c72054b6d..e893838655 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -91,7 +91,7 @@ the key is marked as being expired and accesses to it fail with the error
If not deleted, updated, or replaced, then, after a set amount of time,
an expired key is automatically removed (garbage collected)
along with all links to it,
-and attempts to access the key will fail with the error
+and attempts to access the key fail with the error
.BR ENOKEY .
.TP
Reference count
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index 7618f2db8f..d762df2031 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -81,7 +81,7 @@ This behavior reflects the fact that the "init" process
is essential for the correct operation of a PID namespace.
In this case, a subsequent
.BR fork (2)
-into this PID namespace will fail with the error
+into this PID namespace fail with the error
.BR ENOMEM ;
it is not possible to create a new processes in a PID namespace whose "init"
process has terminated.
@@ -97,7 +97,7 @@ if the first child subsequently created by a
.BR fork (2)
terminates, then subsequent calls to
.BR fork (2)
-will fail with
+fail with
.BR ENOMEM .
.PP
Only signals for which the "init" process has established a signal handler
diff --git a/man7/sched.7 b/man7/sched.7
index 94789e565b..c8073467a4 100644
--- a/man7/sched.7
+++ b/man7/sched.7
@@ -356,7 +356,7 @@ A call to
.BR fork (2)
by a thread scheduled under the
.B SCHED_DEADLINE
-policy will fail with the error
+policy fails with the error
.BR EAGAIN ,
unless the thread has its reset-on-fork flag set (see below).
.PP
diff --git a/man7/thread-keyring.7 b/man7/thread-keyring.7
index 14ac958958..67c6aa87be 100644
--- a/man7/thread-keyring.7
+++ b/man7/thread-keyring.7
@@ -41,7 +41,7 @@ A thread keyring is destroyed when the thread that refers to it terminates.
Initially, a thread does not have a thread keyring.
If a thread doesn't have a thread keyring when it is accessed,
then it will be created if it is to be modified;
-otherwise the operation will fail with the error
+otherwise the operation fails with the error
.BR ENOKEY .
.SH SEE ALSO
.ad l