aboutsummaryrefslogtreecommitdiffstats
path: root/man2
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2007-07-08 12:39:24 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2007-07-08 12:39:24 +0000
commite0bf91271fef617111632b10e00a06f9800488bd (patch)
tree208baa14da80f6fc00cdfb7a7fcb1d3cb1d0b291 /man2
parent9ec940751d268c66877a1fd4846c843028df0131 (diff)
downloadman-pages-e0bf91271fef617111632b10e00a06f9800488bd.tar.gz
Removed trailing white space at end of lines
Diffstat (limited to 'man2')
-rw-r--r--man2/chown.24
-rw-r--r--man2/madvise.22
-rw-r--r--man2/setpgid.24
-rw-r--r--man2/sigqueue.22
-rw-r--r--man2/spu_create.26
-rw-r--r--man2/spu_run.218
-rw-r--r--man2/stat.214
-rw-r--r--man2/syscalls.212
-rw-r--r--man2/uname.22
9 files changed, 32 insertions, 32 deletions
diff --git a/man2/chown.2 b/man2/chown.2
index f95a858293..73d2942c84 100644
--- a/man2/chown.2
+++ b/man2/chown.2
@@ -231,13 +231,13 @@ main(int argc, char *argv[])
}
uid = pwd\->pw_uid;
- }
+ }
if (chown(argv[2], uid, \-1) == \-1) {
perror("chown");
exit(EXIT_FAILURE);
} /* if */
-
+
exit(EXIT_SUCCESS);
} /* main */
.fi
diff --git a/man2/madvise.2 b/man2/madvise.2
index 22b546b24f..d743464202 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -99,7 +99,7 @@ and its associated backing store.
Currently,
.\" 2.6.18-rc5
only shmfs/tmpfs supports this; other filesystems return file with the
-error
+error
.BR ENOSYS .
.\" Databases want to use this feature to drop a section of their
.\" bufferpool (shared memory segments) - without writing back to
diff --git a/man2/setpgid.2 b/man2/setpgid.2
index 32885f3d55..3afe606d4d 100644
--- a/man2/setpgid.2
+++ b/man2/setpgid.2
@@ -59,7 +59,7 @@ setpgid, getpgid, setpgrp, getpgrp \- set/get process group
.sp
.BR "int setpgrp(void);" " /* System V version */"
.br
-.BI "int setpgrp(pid_t " pid ", pid_t " pgid );
+.BI "int setpgrp(pid_t " pid ", pid_t " pgid );
/* BSD version */
.sp
.in -4n
@@ -108,7 +108,7 @@ is used to move a process from one process
group to another (as is done by some shells when creating pipelines),
both process groups must be part of the same session (see
.BR setsid (2)
-and
+and
.BR credentials (7)).
In this case,
the \fIpgid\fP specifies an existing process group to be joined and the
diff --git a/man2/sigqueue.2 b/man2/sigqueue.2
index 67ccf3cbe4..3bb2ff35a4 100644
--- a/man2/sigqueue.2
+++ b/man2/sigqueue.2
@@ -125,7 +125,7 @@ structure that will be supplied to the receiving process's
signal handler or returned by the receiving process's
.BR sigtimedwait (2)
call.
-Inside the glibc
+Inside the glibc
.BR sigqueue ()
wrapper, this argument,
.IR info ,
diff --git a/man2/spu_create.2 b/man2/spu_create.2
index 46a25df320..1df0c8fa7b 100644
--- a/man2/spu_create.2
+++ b/man2/spu_create.2
@@ -70,12 +70,12 @@ constant:
.B SPU_RAWIO
Allow mapping of some of the hardware registers of the SPU into user
space.
-This flag requires the
+This flag requires the
.B CAP_SYS_RAWIO
capability.
.PP
The new directory and files are created in the SPUFS with the
-permissions set by the
+permissions set by the
.I mode
argument minus those set in the process's
.BR umask (2).
@@ -160,7 +160,7 @@ Note however, that
.BR spu_create ()
is meant to be used from libraries that implement a more abstract
interface to SPUs, not to be used from regular applications.
-See
+See
.I http://www.bsc.es/projects/deepcomputing/linuxoncell/
for the recommended libraries.
.SH BUGS
diff --git a/man2/spu_run.2 b/man2/spu_run.2
index b0285e2634..96c68a4863 100644
--- a/man2/spu_run.2
+++ b/man2/spu_run.2
@@ -33,26 +33,26 @@ spu_run \- execute an spu context
", unsigned int *" event ");"
.fi
.SH DESCRIPTION
-The
+The
.BR spu_run ()
-system call is used on PowerPC machines that implement the
-Cell Broadband Engine Architecture in order to access Synergistic
+system call is used on PowerPC machines that implement the
+Cell Broadband Engine Architecture in order to access Synergistic
Processor Units (SPUs).
The
.I fd
-argument is a file descriptor returned by
+argument is a file descriptor returned by
.BR spu_create (2)
that addresses a specific SPU context.
When the context gets
scheduled to a physical SPU, it starts execution at the instruction
-pointer passed in
+pointer passed in
.IR npc .
-Execution of SPU code happens synchronously, meaning that
+Execution of SPU code happens synchronously, meaning that
.BR spu_run ()
does not return while the SPU is still running.
If there is a need
-to execute SPU code in parallel with other code on either the
+to execute SPU code in parallel with other code on either the
main CPU or other SPUs, a new thread of execution must be created
first, using the
.BR pthread_create (3)
@@ -115,7 +115,7 @@ register.
On error it returns \-1 and sets
.I errno
to one of the error codes listed below.
-The
+The
.I spu_status
register value is a bit mask of status codes and
optionally a 14-bit code returned from the stop-and-signal
@@ -203,7 +203,7 @@ Note however, that
.BR spu_run ()
is meant to be used from libraries that implement a more abstract
interface to SPUs, not to be used from regular applications.
-See
+See
.I http://www.bsc.es/projects/deepcomputing/linuxoncell/
for the recommended libraries.
.SH BUGS
diff --git a/man2/stat.2 b/man2/stat.2
index 6d6d6388b9..4654e2ae99 100644
--- a/man2/stat.2
+++ b/man2/stat.2
@@ -446,7 +446,7 @@ behavior of old binaries does not change.
The glibc
.BR stat ()
wrapper function hides these details from applications,
-ensuring that new applications linked against
+ensuring that new applications linked against
the current library automatically use the current implementation,
and that binary compatibility is not broken for older binaries.
Similar remarks apply for
@@ -455,12 +455,12 @@ and
.BR lstat (2).
.\"
.\" A note from Andries Brouwer, July 2007
-.\"
-.\" > Is the story not rather more complicated for some calls like
+.\"
+.\" > Is the story not rather more complicated for some calls like
.\" > stat(2)?
-.\"
+.\"
.\" Yes and no, mostly no. See /usr/include/sys/stat.h .
-.\"
+.\"
.\" The idea is here not so much that syscalls change, but that
.\" the definitions of struct stat and of the types dev_t and mode_t change.
.\" This means that libc (even if it does not call the kernel
@@ -472,14 +472,14 @@ and
.\" uses. Each (almost each) occurrence of stat() is replaced by
.\" an occurrence of xstat() where the first parameter of xstat()
.\" is this version number _STAT_VER.
-.\"
+.\"
.\" Now, also the definitions used by the kernel change.
.\" But glibc copes with this in the standard way, and the
.\" struct stat as returned by the kernel is repacked into
.\" the struct stat as expected by the application.
.\" Thus, _STAT_VER and this setup cater for the application-libc
.\" interface, rather than the libc-kernel interface.
-.\"
+.\"
.\" (Note that the details depend on gcc being used as c compiler.)
.SH EXAMPLE
The following program calls
diff --git a/man2/syscalls.2 b/man2/syscalls.2
index 320afe8dac..0320231561 100644
--- a/man2/syscalls.2
+++ b/man2/syscalls.2
@@ -71,11 +71,11 @@ Note the following points:
Where no kernel version is indicated,
the system call appeared in kernel 2.0 or earlier.
.\" kernel 1.2 was started from a branch of 1.0.6
-.\"
+.\"
.\" Was kernel 2.0 started from a branch of 1.2.10?
.\" At least from the timestamps of the tarballs of
.\" of 1.2.10 and 1.3.0, that's how it looks, but in
-.\" fact the diff doesn't seem very clear, the
+.\" fact the diff doesn't seem very clear, the
.\" 1.3.0 .tar.bz is much bigger (2.0 MB) than the
.\" 1.2.10 .tar.bz2 (1.8 MB), and AEB points out the
.\" timestamps of some files in 1.3.0 seem to be older
@@ -533,7 +533,7 @@ and similarly System V IPC calls are multiplexed through
Note the following points:
.IP * 3
Although slots are reserved for them in the system call table,
-the following system calls are not implemented in the standard kernel:
+the following system calls are not implemented in the standard kernel:
.BR afs_syscall (2), \" __NR_afs_syscall is 53 on Linux 2.6.22/i386
.BR break (2), \" __NR_break is 17 on Linux 2.6.22/i386
.BR ftime (2), \" __NR_ftime is 35 on Linux 2.6.22/i386
@@ -567,7 +567,7 @@ The slot for
.BR phys (2)
is in use since kernel 2.1.116 for
.BR umount (2);
-.BR phys (2)
+.BR phys (2)
will never be implemented.
.IP *
The
@@ -741,10 +741,10 @@ and similarly
.\" .IR sys_llseek ()
.\" and
.\" .IR sys_sysctl ().
-.\"
+.\"
.\" In kernel 2.1.81,
.\" .BR lchown (2)
-.\" and
+.\" and
.\" .BR chown (2)
.\" were swapped; that is,
.\" .BR lchown (2)
diff --git a/man2/uname.2 b/man2/uname.2
index 44299aa6ab..5827b35b6f 100644
--- a/man2/uname.2
+++ b/man2/uname.2
@@ -141,7 +141,7 @@ the third also uses 65 but adds the \fIdomainname\fP field.
The glibc
.BR uname ()
wrapper function hides these details from applications,
-ensuring that new applications linked against
+ensuring that new applications linked against
the current library automatically use the current implementation,
and that binary compatibility is not broken for older binaries.
.SH "SEE ALSO"