</example>
<p>The <code>-l</code> option tells truss to log the ID of the
- LWP (lightweight process--Solaris's form of kernel-level thread)
+ LWP (lightweight process--Solaris' form of kernel-level thread)
that invokes each system call.</p>
<p>Other systems may have different system call tracing utilities
<p>Next, the worker thread puts the connection to the client (file
descriptor 9) in non-blocking mode. The <code>setsockopt(2)</code>
and <code>getsockopt(2)</code> calls are a side-effect of how
- Solaris's libc handles <code>fcntl(2)</code> on sockets.</p>
+ Solaris' libc handles <code>fcntl(2)</code> on sockets.</p>
<example>
<pre>/65: read(9, " G E T / 1 0 k . h t m".., 8000) = 97</pre>
of the number of requests. It works as follows:</p>
<p><dfn>lbfactor</dfn> is <em>how much we expect this worker
- to work</em>, or <em>the workers's work quota</em>. This is
+ to work</em>, or <em>the workers' work quota</em>. This is
a normalized value representing their "share" of the amount of
work to be done.</p>
<p>The Server consists of a main, parent process and a small, static
number of child processes.</p>
- <p>The parent process's job is to manage the child processes. This
+ <p>The parent process' job is to manage the child processes. This
involves spawning children as required to ensure there are always
<directive module="mpm_common">StartServers</directive> processes
accepting connections.</p>