Update Question 10.25:

- Add non-breakable spaces for better rendering

Approved by:  gabor
This commit is contained in:
Gabor Pali 2008-06-21 07:44:21 +00:00
parent 92b2af15b1
commit a6a3cce6eb
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=32339

View file

@ -6404,12 +6404,12 @@ options SYSVMSG # enable for messaging</programlisting>
<qandaentry>
<question id="statd-mem-leak">
<para>Why is <command>rpc.statd</command> using 256 megabytes of
<para>Why is <command>rpc.statd</command> using 256&nbsp;MB of
memory?</para>
</question>
<answer>
<para>No, there is no memory leak, and it is not using 256 Mbytes
<para>No, there is no memory leak, and it is not using 256&nbsp;MB
of memory. For convenience, <command>rpc.statd</command> maps an
obscene amount of memory into its address space.
There is nothing terribly wrong with this from a technical
@ -6422,7 +6422,7 @@ options SYSVMSG # enable for messaging</programlisting>
it with a generous size. This is very evident from the source
code, where one can see that the length argument to &man.mmap.2;
is <literal>0x10000000</literal>, or one sixteenth of the
address space on an IA32, or exactly 256MB.</para>
address space on an IA32, or exactly 256&nbsp;MB.</para>
</answer>
</qandaentry>