Removed trailing white space at end of lines

man2/dup.2

@@ -143,7 +143,7 @@ and
 .B EINTR
 The
 .BR dup2 ()
-or    
+or
 .BR dup3 ()
 call was interrupted by a signal; see
 .BR signal (7).

man2/epoll_create.2

@@ -72,13 +72,13 @@ to obtain different behavior:
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)
 for reasons why this may be useful.
 .SH "RETURN VALUE"
-On success, 
+On success,
 these system calls
 return a non-negative file descriptor.
 On error, \-1 is returned, and

man2/eventfd.2

@@ -53,7 +53,7 @@ to achieve the same result.
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man2/inotify_init.2

@@ -63,7 +63,7 @@ to achieve the same result.
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man2/signalfd.2

@@ -86,7 +86,7 @@ to achieve the same result.
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man2/socket.2

@@ -172,7 +172,7 @@ to achieve the same result.
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man2/timerfd_create.2

@@ -92,7 +92,7 @@ to achieve the same result.
 Set the close-on-exec
 .RB ( FD_CLOEXEC )
 flag on the new file descriptor.
-See the description of the 
+See the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man3/getaddrinfo.3

@@ -543,7 +543,7 @@ This could occur, for example, if
 .I hints.ai_socktype
 and
 .I hints.ai_protocol
-are inconsistent (e.g., 
+are inconsistent (e.g.,
 .BR SOCK_DGRAM
 and
 .BR IPPROTO_TCP ,

man3/popen.3

@@ -86,7 +86,7 @@ this argument can additionally include the letter \(aqe\(aq,
 which causes the close-on-exec flag
 .RB ( FD_CLOEXEC )
 to be set on the underlying file descriptor;
-see the description of the 
+see the description of the
 .B O_CLOEXEC
 flag in
 .BR open (2)

man3/pthread_attr_init.3

@@ -45,7 +45,7 @@ and then the object can be used in one or more
 .BR pthread_create (3)
 calls that create threads.
 
-Calling 
+Calling
 .BR pthread_attr_init ()
 on a thread attributes object that has already been initialized
 results in undefined behavior.

man3/pthread_attr_setdetachstate.3

@@ -48,7 +48,7 @@ the thread attributes object
 .I attr
 will be created in a joinable or a detached state.
 
-The following values may be specified in 
+The following values may be specified in
 .IR detachstate :
 .TP
 .B PTHREAD_CREATE_DETACHED
@@ -96,7 +96,7 @@ or detached using
 see
 .BR pthread_create (3).
 
-It is an error to specify the thread ID of 
+It is an error to specify the thread ID of
 a thread that was created in a detached state
 in a later call to
 .BR pthread_detach (3)

man3/pthread_attr_setguardsize.3

@@ -94,7 +94,7 @@ error if
 .I attr
 or
 .I guardsize
-is invalid.  
+is invalid.
 On Linux these functions always succeed
 (but portable and future-proof applications should nevertheless
 handle a possible error return).
@@ -140,7 +140,7 @@ The obsolete LinuxThreads implementation did the right thing,
 allocating extra space at the end of the stack for the guard area.
 .\" glibc includes the guardsize within the allocated stack size,
 .\" which looks pretty clearly to be in violation of POSIX.
-.\" 
+.\"
 .\" Filed bug, 22 Oct 2008:
 .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6973
 .\"

man3/pthread_attr_setstackaddr.3

@@ -36,7 +36,7 @@ set/get stack address attribute in thread attributes object
 .sp
 Compile and link with \fI\-pthread\fP.
 .SH DESCRIPTION
-These functions are obsolete: 
+These functions are obsolete:
 .B do not use them.
 Use
 .BR pthread_attr_setstack (3)

man3/pthread_create.3

@@ -91,7 +91,7 @@ in subsequent calls to other pthreads functions.
 
 The new thread inherits a copy of the creating thread's signal mask
 .RB ( pthread_sigmask (3)).
-The set of pending signals for the new thread is empty 
+The set of pending signals for the new thread is empty
 .RB ( sigpending (2)).
 The new thread does not inherit the creating thread's
 alternate signal stack

man4/console_ioctl.4

@@ -24,7 +24,7 @@
 .\" Modified, Sun Feb 26 15:04:20 1995, faith@cs.unc.edu
 .\" Modified, Thu Apr 20 22:08:17 1995, jrv@vanzandt.mv.com
 .\" Modified, Mon Sep 18 22:32:47 1995, hpa@storm.net (H. Peter Anvin)
-.\" FIXME The following are not documented: 
+.\" FIXME The following are not documented:
 .\"     KDFONTOP (since 2.1.111)
 .\"     KDGKBDIACRUC (since 2.6.24)
 .\"     KDSKBDIACR

man5/utmp.5

@@ -49,7 +49,7 @@ modifications of system files if you leave
 .I utmp
 writable to any user other than the owner and group owner of the file.
 .PP
-The file is a sequence of 
+The file is a sequence of
 .I utmp
 structures,
 declared as follows in

man7/inotify.7

@@ -37,7 +37,7 @@ for the directory itself, and for files inside the directory.
 
 The following system calls are used with this API:
 .BR inotify_init (2)
-(or 
+(or
 .BR inotify_init1 (2)),
 .BR inotify_add_watch (2),
 .BR inotify_rm_watch (2),

man8/ld.so.8

@@ -181,8 +181,8 @@ Old versions of ld\-linux.so.1 also supported
 .\" Document LD_AUDIT ("Install audit libraries for glibc")
 .\" new in glibc 2.4
 .\" ignored in set-user-ID and set-group-ID programs
-.\" 
+.\"
-.\" For some info, see Solaris Linker and Libraries Guide, 
+.\" For some info, see Solaris Linker and Libraries Guide,
 .\" "Runtime Linker Auditing Interface"
 .TP
 .B LD_BIND_NOT
@@ -240,7 +240,7 @@ For security reasons, since glibc 2.4,
 is ignored for set-user-ID/set-group-ID binaries.
 .\" Only used if $ORIGIN can't be determined by normal means
 .\" (from the origin path saved at load time, or from /proc/self/exe)?
-.\" 
+.\"
 .\" FIXME
 .\" Document LD_POINTER_GUARD
 .\" Since glibc 2.4