Attachment 19076 Details for Bug 34036 – file.diff

[patch] file.diff

file.diff (text/plain), 4.44 KB, created by darklogik on 2002-01-18 15:30:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: darklogik

Created: 2002-01-18 15:30:00 UTC

Size: 4.44 KB

patch

obsolete

>*** chapter.sgml.old	Thu Jan 17 21:16:28 2002
>--- chapter.sgml	Thu Jan 17 23:48:53 2002
>***************
>*** 503,524 ****
>        <secondary>maxusers</secondary>
>      </indexterm>
>  
>!     <programlisting>maxusers          32</programlisting>
>  
>!     <para>The <literal>maxusers</literal> option sets the size of a number
>!       of important system tables.  This number is supposed to be roughly
>        equal to the number of simultaneous users you expect to have on your
>!       machine.  However, under normal circumstances, you will want to set
>!       <literal>maxusers</literal> to at least 4, especially if you are
>!       using the X Window System or compiling software.  The reason is that
>!       the most important table set by <literal>maxusers</literal> is the
>!       maximum number of processes,  which is set to <literal>20 + 16 *
>!       maxusers</literal>, so if you set <literal>maxusers</literal> to 1,
>!       then you can only have 36 simultaneous processes, including the 18
>!       or so that the system starts up at boot time, and the 15 or so you
>!       will probably create when you start the X Window System.  Even a
>!       simple task like reading a manual page will start up nine processes to
>!       filter, decompress, and view it.  Setting
>        <literal>maxusers</literal> to 64 will allow you to have up to 1044
>        simultaneous processes, which should be enough for nearly all uses.
>        If, however, you see the dreaded <errortype>proc table
>--- 503,533 ----
>        <secondary>maxusers</secondary>
>      </indexterm>
>  
>!     <programlisting>maxusers          0</programlisting>
>  
>!     <para>The <literal>maxusers</literal> option will set the size for many
>!       important system tables.  This number is supposed to be roughly
>        equal to the number of simultaneous users you expect to have on your
>!       machine.  Since 4.5-RELEASE, however, the <literal>maxusers</literal>
>!       option is auto-tuning, and set at 0 by default in the configuration.
>!       Using a value of 0 will let the system automatically select the
>!       appropriate value based on physical system memory.
>!       This value can be obtained after booting, by looking at
>!       <literal>kern.maxusers</literal>, and modified at boot-time by changing the
>!       <filename>kernel</filename> configuration, or just by updating
>!       <literal>kern.maxusers</literal> in the <filename>/boot/loader.conf</filename>
>!       file.  Using a value other than 0, will cause the <filename>kernel</filename>
>!       to use the old style <literal>maxusers</literal>, and it is
>!       recommended you set this value no less than 4 if you wish to manually
>!       enter it, specially if you will be using the X Window System or compiling
>!       software.  The reason for this is that the most important table set by
>!       <literal>maxusers</literal> is the maximum number of processes,
>!       which is set to <literal>20 + 16 * maxusers</literal>, so if you set
>!       <literal>maxusers</literal> to 1, then you can only have 36 simultaneous
>!       processes, including the 18 or so that the system starts up at boot
>!       time, and the 15 or so you will probably create when you start the X
>!       Window System.  Even a simple task like reading a manual page will start
>!       up nine processes to filter, decompress, and view it.  Setting
>        <literal>maxusers</literal> to 64 will allow you to have up to 1044
>        simultaneous processes, which should be enough for nearly all uses.
>        If, however, you see the dreaded <errortype>proc table
>***************
>*** 677,682 ****
>--- 686,705 ----
>        -C</command>, which will display any <command>write</command>,
>        <command>talk</command>, and any other messages you receive, as well
>        as any console messages sent by the kernel.</para>
>+ 
>+     <programlisting>options	     SOFTUPDATES         #Softupdates</programlisting>
>+ 
>+     <para>This options allows for faster dist writing.</para>
>+ 
>+       <note>
>+         <para><option>SOFTUPDATES</option> are already enabled in the
>+         <filename>GENERIC</filename> kernel, but they are not turned on
>+ 	by default.  You need to set this option yourself using the
>+ 	&man.tunefs.8; command, and specifying the <option>-n</option>
>+ 	option.  Please read over the
>+ 	<filename>/usr/src/sys/ufs/ffs/README.softupdates</filename> file before
>+ 	setting this option</para>
>+       </note>
>  
>      <programlisting>options          USERCONFIG          #boot -c editor</programlisting>

Actions: View | Diff

Attachments on bug 34036: 19076