Removed trailing white space at end of lines

This commit is contained in:
Michael Kerrisk 2008-11-25 21:44:53 -05:00
parent 59fa7953f6
commit a113945faa
14 changed files with 24 additions and 24 deletions

View File

@ -40,7 +40,7 @@ values in a
as returned by
.BR times (2)).
Note: some shells (e.g.,
Note: some shells (e.g.,
.BR bash (1))
have a built-in
.B time

View File

@ -233,7 +233,7 @@ If this flag is not set, then (as with
the new process has its own I/O context.
.\" The following based on text from Jens Axboe
The I/O context is the I/O scope of the disk scheduler (i.e,
The I/O context is the I/O scope of the disk scheduler (i.e,
what the I/O scheduler uses to model scheduling of a process's I/O).
If processes share the same I/O context,
they are treated as one by the I/O scheduler.

View File

@ -190,7 +190,7 @@ and passing the value returned from a call to
will set the attribute for the main thread of the thread group.
(If you are using the POSIX threads API, then use
.B pthread_setaffinity_np (3)
instead of
instead of
.BR sched_setaffinity ().)
A child created via

View File

@ -37,7 +37,7 @@ sysctl \- read/write system parameters
.BI "int _sysctl(struct __sysctl_args *" args );
.fi
.SH DESCRIPTION
.B Do not use this system call!
.B Do not use this system call!
See NOTES.
The

View File

@ -25,7 +25,7 @@
.TH CPU_SET 2 2008-11-14 "Linux" "Linux Programmer's Manual"
.SH NAME
CPU_SET, CPU_CLR, CPU_ISSET, CPU_ZERO, CPU_COUNT,
CPU_AND, CPU_OR, CPU_XOR, CPU_EQUAL,
CPU_AND, CPU_OR, CPU_XOR, CPU_EQUAL,
CPU_ALLOC, CPU_ALLOC_SIZE, CPU_FREE,
CPU_SET_S, CPU_CLR_S, CPU_ISSET_S, CPU_ZERO_S,
CPU_COUNT_S, CPU_AND_S, CPU_OR_S, CPU_XOR_S, CPU_EQUAL_S \-
@ -43,11 +43,11 @@ macros for manipulating CPU sets
.sp
.BI "void CPU_COUNT(cpu_set_t *" set );
.sp
.BI "void CPU_AND(cpu_set_t *" destset ,
.BI "void CPU_AND(cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.BI "void CPU_OR(cpu_set_t *" destset ,
.BI "void CPU_OR(cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.BI "void CPU_XOR(cpu_set_t *" destset ,
.BI "void CPU_XOR(cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.sp
.BI "int CPU_EQUAL(cpu_set_t *" set1 ", cpu_set_t *" set2 );
@ -64,11 +64,11 @@ macros for manipulating CPU sets
.sp
.BI "void CPU_COUNT_S(size_t " setsize ", cpu_set_t *" set );
.sp
.BI "void CPU_AND_S(size_t " setsize ", cpu_set_t *" destset ,
.BI "void CPU_AND_S(size_t " setsize ", cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.BI "void CPU_OR_S(size_t " setsize ", cpu_set_t *" destset ,
.BI "void CPU_OR_S(size_t " setsize ", cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.BI "void CPU_XOR_S(size_t " setsize ", cpu_set_t *" destset ,
.BI "void CPU_XOR_S(size_t " setsize ", cpu_set_t *" destset ,
.BI " cpu_set_t *" srcset1 ", cpu_set_t *" srcset2 );
.sp
.BI "int CPU_EQUAL_S(size_t " setsize ", cpu_set_t *" set1 \

View File

@ -90,7 +90,7 @@ used to represent CPU sets.)
A CPU in the affinity mask of the thread attributes object referred to by
.I attr
lies outside the range specified by
.IR cpusetsize
.IR cpusetsize
(i.e.,
.IR cpuset / cpusetsize
is too small).

View File

@ -104,7 +104,7 @@ as the thread's exit status.
(Joining with a thread is the only way to know that cancellation
has completed.)
.SH RETURN VALUE
On success,
On success,
.BR pthread_cancel ()
returns 0;
on error, it returns a non-zero error number.

View File

@ -95,7 +95,7 @@ and at the same lexical nesting level.
during the execution of a specified section of code.)
Calling
.BR longjmp (3)
.BR longjmp (3)
.RB ( siglongjmp (3))
produces undefined results if any call has been made to
.BR pthread_cleanup_push ()
@ -106,7 +106,7 @@ was filled by
.BR setjmp (3)
.RB ( sigsetjmp (3)).
Likewise, calling
.BR longjmp (3)
.BR longjmp (3)
.RB ( siglongjmp (3))
from inside a clean-up handler produces undefined results
unless the jump buffer was also filled by
@ -122,7 +122,7 @@ There are no errors.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
On Linux, the
On Linux, the
.BR pthread_cleanup_push ()
and
.BR pthread_cleanup_pop ()
@ -139,7 +139,7 @@ says that the effect of using
.IR continue ,
or
.IR goto
to prematurely leave a block bracketed
to prematurely leave a block bracketed
.BR pthread_cleanup_push ()
and
.BR pthread_cleanup_pop ()

View File

@ -139,7 +139,7 @@ family of functions) may be left in an inconsistent state
if cancellation occurs in the middle of the function call.
Consequently, clean-up handlers cease to be useful.
Functions that can be safely asynchronously canceled are called
.IR "async-cancel-safe functions" .
.IR "async-cancel-safe functions" .
POSIX.1-2001 only requires that
.BR pthread_cancel (3),
.BR pthread_setcancelstate (),

View File

@ -215,7 +215,7 @@ rather than the thread attributes object.
Note that if we had omitted the
.IR "\-i\ i"
option, the output would have been the same, since
option, the output would have been the same, since
.BR PTHREAD_INHERIT_SCHED
is the default for the inherit scheduler attribute.
.SS Program source

View File

@ -44,7 +44,7 @@ tuned by the
interfaces described below.
When there is no positive feedback for an existing mapping after some
time (see the
time (see the
.I /proc
interfaces below), a neighbor cache entry is considered stale.
Positive feedback can be gotten from a higher layer; for example from

View File

@ -80,12 +80,12 @@ packets.
.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt
If disabled, ICMP error messages are sent with the primary address of
the exiting interface.
If enabled, the message will be sent with the primary address of
the interface that received the packet that caused the ICMP error.
This is the behavior that many network administrators will expect from
a router.
And it can make debugging complicated network layouts much easier.
And it can make debugging complicated network layouts much easier.
Note that if no primary address exists for the interface selected,
then the primary address of the first non-loopback interface that

View File

@ -782,7 +782,7 @@ The default value is 16K bytes.
.\" True in Linux 2.4 and 2.6
If larger send buffer sizes are desired, this value
should be increased (to affect all sockets).
To employ large TCP windows, the
To employ large TCP windows, the
.I /proc/sys/net/ipv4/tcp_window_scaling
must be set to a non-zero value (default).
.TP

View File

@ -145,7 +145,7 @@ this number, UDP starts to moderate memory usage.
.TP
.I pressure
This value was introduced to follow the format of
.IR tcp_mem
.IR tcp_mem
(see
.BR tcp (7)).
.TP