summaryrefslogtreecommitdiff
path: root/manual/resource.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2002-06-30 04:04:20 +0000
committerUlrich Drepper <drepper@redhat.com>2002-06-30 04:04:20 +0000
commit95fdc6a0f61a389e92a6b84250c2286b4808b626 (patch)
tree54afe4d2de7ab4aeb9a6d0943ab90d8ddc794c0a /manual/resource.texi
parent8b8cc76fa47fe0819e5e52e29c6674e799df646e (diff)
Update.
2002-06-19 Steven Munroe <sjmunroe@vnet.ibm.com> * Examples/ex9.c (main): Use list of children and join them. (thread): Do not call exit.
Diffstat (limited to 'manual/resource.texi')
-rw-r--r--manual/resource.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/manual/resource.texi b/manual/resource.texi
index 3beb939006..9d2e17bed4 100644
--- a/manual/resource.texi
+++ b/manual/resource.texi
@@ -546,7 +546,7 @@ any one time is equal to the number of CPUs, you can easily extrapolate
the information.
The functions described in this section are all defined by the POSIX.1
-and POSIX.1b standards (the @code{sched...} functions are POSIX.1b).
+and POSIX.1b standards (the @code{sched@dots{}} functions are POSIX.1b).
However, POSIX does not define any semantics for the values that these
functions get and set. In this chapter, the semantics are based on the
Linux kernel's implementation of the POSIX standard. As you will see,
@@ -656,7 +656,7 @@ the high priority process group. All the priority in the world won't
stop an interrupt handler from running and delivering a signal to the
process if you hit Control-C.
-Some systems use absolute priority as a means of allocating a fixed
+Some systems use absolute priority as a means of allocating a fixed
percentage of CPU time to a process. To do this, a super high priority
privileged process constantly monitors the process' CPU usage and raises
its absolute priority when the process isn't getting its entitled share