capget.2, fanotify_init.2, fcntl.2, ioctl_tty.2, madvise.2, mbind.2, prctl.2, sched_setaffinity.2, hash.3, isgreater.3, posix_fallocate.3, sigvec.3, full.4, sd.4, wavelan.4, core.5, host.conf.5, epoll.7, signal.7, unix.7, user_namespaces.7: wfix (will fail --> fail/fails)

Reported-by: Pedro Alves <palves@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2017-10-20 12:36:42 +02:00 · 2017-10-20 12:36:42 +02:00 · a23d8efafc
parent 6e2767983c
commit a23d8efafc
21 changed files with 31 additions and 31 deletions
--- a/man2/capget.2
+++ b/man2/capget.2
@ -176,7 +176,7 @@ On error, \-1 is returned, and
 .I errno
 is set appropriately.
 .PP
-The calls will fail with the error
+The calls fail with the error
 .BR EINVAL ,
 and set the
 .I version
--- a/man2/fanotify_init.2
+++ b/man2/fanotify_init.2
@ -128,7 +128,7 @@ for the file descriptor.
 Reading from the file descriptor will not block.
 Instead, if no data is available,
 .BR read (2)
-will fail with the error
+fails with the error
 .BR EAGAIN .
 .TP
 .B FAN_UNLIMITED_QUEUE
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@ -1434,7 +1434,7 @@ flag as well as
 .BR truncate (2)
 and
 .BR ftruncate (2).
-Those calls will fail with
+Those calls fail with
 .B EPERM
 if you try to shrink the file in question.
 Increasing the file size is still possible.
@ -1448,7 +1448,7 @@ beyond the end of the file,
 .BR ftruncate (2),
 and
 .BR fallocate (2).
-These calls will fail with
+These calls fail with
 .B EPERM
 if you use them to increase the file size.
 If you keep the size or shrink it, those calls still work as expected.
@ -1473,7 +1473,7 @@ and
 (only in combination with the
 .B FALLOC_FL_PUNCH_HOLE
 flag).
-Those calls will fail with
+Those calls fail with
 .B EPERM
 if this seal is set.
 Furthermore, trying to create new shared, writable memory-mappings via
@ -1485,7 +1485,7 @@ Using the
 .B F_ADD_SEALS
 operation to set the
 .B F_SEAL_WRITE
-seal will fail with
+seal fails with
 .B EBUSY
 if any writable, shared mapping exists.
 Such mappings must be unmapped before you can add this seal.
--- a/man2/ioctl_tty.2
+++ b/man2/ioctl_tty.2
@ -281,9 +281,9 @@ Set the foreground process group ID of this terminal.
 .TP
 .BI "TIOCGSID	pid_t *" argp
 Get the session ID of the given terminal.
-This will fail with
+This fails fail with the error
 .B ENOTTY
-in case the terminal is not a master pseudoterminal
+if the terminal is not a master pseudoterminal
 and not our controlling terminal.
 Strange.
 .SS Exclusive mode
@ -293,7 +293,7 @@ Put the terminal into exclusive mode.
 No further
 .BR open (2)
 operations on the terminal are permitted.
-(They will fail with
+(They fail fail with
 .BR EBUSY ,
 except for a process with the
 .BR CAP_SYS_ADMIN
--- a/man2/madvise.2
+++ b/man2/madvise.2
@ -198,7 +198,7 @@ any filesystem which supports the
 .BR FALLOC_FL_PUNCH_HOLE
 mode also supports
 .BR MADV_REMOVE .
-Hugetlbfs will fail with the error
+Hugetlbfs fails with the error
 .BR EINVAL
 and other filesystems fail with the error
 .BR EOPNOTSUPP .
--- a/man2/mbind.2
+++ b/man2/mbind.2
@ -289,7 +289,7 @@ and
 .I mode
 is not
 .BR MPOL_DEFAULT ,
-then the call will fail with the error
+then the call fails with the error
 .B EIO
 if the existing pages in the memory range don't follow the policy.
 .\" According to the kernel code, the following is not true
@ -306,7 +306,7 @@ in the memory range so that they follow the policy.
 Pages that are shared with other processes will not be moved.
 If
 .B MPOL_MF_STRICT
-is also specified, then the call will fail with the error
+is also specified, then the call fails with the error
 .B EIO
 if some pages could not be moved.
 .PP
@ -321,7 +321,7 @@ The calling thread must be privileged
 to use this flag.
 If
 .B MPOL_MF_STRICT
-is also specified, then the call will fail with the error
+is also specified, then the call fails with the error
 .B EIO
 if some pages could not be moved.
 .\" ---------------------------------------------------------------
--- a/man2/prctl.2
+++ b/man2/prctl.2
@ -733,7 +733,7 @@ the bounds directory and placed the location of that directory in the
 .I bndcfgu
 register.
 .IP
-These calls will fail if the CPU or kernel does not support MPX.
+These calls fail if the CPU or kernel does not support MPX.
 Kernel support for MPX is enabled via the
 .BR CONFIG_X86_INTEL_MPX
 configuration option.
--- a/man2/sched_setaffinity.2
+++ b/man2/sched_setaffinity.2
@ -259,7 +259,7 @@ then calls of the form:
 .PP
    sched_getaffinity(pid, sizeof(cpu_set_t), &mask);
 .PP
-will fail with the error
+fail with the error
 .BR EINVAL ,
 the error produced by the underlying system call for the case where the
 .I mask
--- a/man3/hash.3
+++ b/man3/hash.3
@ -139,8 +139,8 @@ ignored and the values specified when the tree was created are used.
 .PP
 If a hash function is specified,
 .I hash_open
-will attempt to determine if the hash function specified is the same as
-the one with which the database was created, and will fail if it is not.
+attempts to determine if the hash function specified is the same as
+the one with which the database was created, and fails if it is not.
 .PP
 Backward-compatible interfaces to the routines described in
 .BR dbm (3),
--- a/man3/isgreater.3
+++ b/man3/isgreater.3
@ -45,7 +45,7 @@ _ISOC99_SOURCE || _POSIX_C_SOURCE\ >=\ 200112L
 The normal relational operations (like
 .BR < ,
 "less than")
-will fail if one of the operands is NaN.
+fail if one of the operands is NaN.
 This will cause an exception.
 To avoid this, C99 defines the macros listed below.
 .PP
--- a/man3/posix_fallocate.3
+++ b/man3/posix_fallocate.3
@ -166,7 +166,7 @@ has been opened with the
 .B O_APPEND
 or
 .B O_WRONLY
-flags, the function will fail with the error
+flags, the function fails with the error
 .BR EBADF .
 .PP
 In general, the emulation is not MT-safe.
--- a/man3/sigvec.3
+++ b/man3/sigvec.3
@ -134,8 +134,8 @@ This field may contain zero or more of the following flags:
 .TP
 .B SV_INTERRUPT
 If the signal handler interrupts a blocking system call,
-then upon return from the handler the system call will not be restarted:
-instead it will fail with the error
+then upon return from the handler the system call s not be restarted:
+instead it fails with the error
 .BR EINTR .
 If this flag is not specified, then system calls are restarted
 by default.
--- a/man4/full.4
+++ b/man4/full.4
@ -46,7 +46,7 @@ and minor device number 7.
 .PP
 Writes to the
 .I /dev/full
-device will fail with an
+device fail with an
 .B ENOSPC
 error.
 This can be used to test how a program handles disk-full errors.
--- a/man4/sd.4
+++ b/man4/sd.4
@ -124,7 +124,7 @@ If the
 .BR ioctl (2)
 parameter is required, and it is NULL, then
 .BR ioctl (2)
-will fail with the error
+fails with the error
 .BR EINVAL .
 .SH FILES
 /dev/sd[a\-h]: the whole device
--- a/man4/wavelan.4
+++ b/man4/wavelan.4
@ -117,7 +117,7 @@ intervals.
 This distribution might be used to calculate the mean value
 and standard deviation of the signal level.
 .SS Specific notes
-This driver will fail to detect some
+This driver fails to detect some
 .B non-NCR/AT&T/Lucent
 Wavelan cards.
 If this happens for you, you must look in the source code on
--- a/man5/core.5
+++ b/man5/core.5
@ -57,7 +57,7 @@ where
 is the ID of the process that dumped core,
 and is created in the current working directory.
 See below for details on naming.)
-Writing the core file will fail if the directory in which
+Writing the core file fails if the directory in which
 it is to be created is nonwritable,
 or if a file with the same name exists and
 is not writable
--- a/man5/host.conf.5
+++ b/man5/host.conf.5
@ -164,7 +164,7 @@ enhance the security of
 It works as follows: after performing a host address lookup,
 the resolver library will perform a hostname lookup for that address.
 If the two hostnames
-do not match, the query will fail.
+do not match, the query fails.
 The default value is
 .IR off .
 .TP
--- a/man7/epoll.7
+++ b/man7/epoll.7
@ -406,7 +406,7 @@ file descriptor into its own file descriptor set?
 .B A4
 The
 .BR epoll_ctl (2)
-call will fail
+call fails
 .RB ( EINVAL ).
 However, you can add an
 .B epoll
--- a/man7/signal.7
+++ b/man7/signal.7
@ -490,10 +490,10 @@ The details vary across UNIX systems;
 below, the details for Linux.
 .PP
 If a blocked call to one of the following interfaces is interrupted
-by a signal handler, then the call will be automatically restarted
+by a signal handler, then the call is automatically restarted
 after the signal handler returns if the
 .BR SA_RESTART
-flag was used; otherwise the call will fail with the error
+flag was used; otherwise the call fails with the error
 .BR EINTR :
 .\" The following system calls use ERESTARTSYS,
 .\" so that they are restartable
--- a/man7/unix.7
+++ b/man7/unix.7
@ -224,7 +224,7 @@ then there is no guarantee that a null terminator is present in
 .SS Pathname socket ownership and permissions
 In the Linux implementation,
 pathname sockets honor the permissions of the directory they are in.
-Creation of a new socket will fail if the process does not have write and
+Creation of a new socket fails if the process does not have write and
 search (execute) permission on the directory in which the socket is created.
 .PP
 On Linux,
--- a/man7/user_namespaces.7
+++ b/man7/user_namespaces.7
@ -752,7 +752,7 @@ then the
 system call can't subsequently be reenabled (by writing
 .RI \(dq allow \(dq
 to the file) in this user namespace.
-(Attempts to do so will fail with the error
+(Attempts to do so fail with the error
 .BR EPERM .)
 This restriction also propagates down to all child user namespaces of
 this user namespace.