Attachment 18350 Details for Bug 33017 – file.diff

[patch] file.diff

file.diff (text/plain), 8.50 KB, created by setantae on 2001-12-19 21:40:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: setantae

Created: 2001-12-19 21:40:00 UTC

Size: 8.50 KB

patch

obsolete

>*** doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml.old	Wed Dec 19 20:42:48 2001
>--- doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml	Wed Dec 19 21:06:29 2001
>***************
>*** 123,129 ****
>  
>  	<para>The size of your <filename>/var</filename> partition
>  	  reflects the intended use of your machine.
>! 	  <filename>/var</filename> is primarily used to hold:
>  	  mailboxes, print spool and log files.  Mailboxes and log
>  	  files, in particular, can grow to unexpected sizes based upon
>  	  how many users are on your system and how long your log files
>--- 123,129 ----
>  
>  	<para>The size of your <filename>/var</filename> partition
>  	  reflects the intended use of your machine.
>! 	  <filename>/var</filename> is primarily used to hold
>  	  mailboxes, print spool and log files.  Mailboxes and log
>  	  files, in particular, can grow to unexpected sizes based upon
>  	  how many users are on your system and how long your log files
>***************
>*** 225,231 ****
>  	  that shifting them more towards the edge of the disk will not
>  	  lead to a significant performance improvement whereas moving
>  	  <filename>/var</filename> to the edge can have a huge impact.
>! 	  Finally, there are safety concerns.  Having a small neat root
>  	  partition that is essentially read-only gives it a greater
>  	  chance of surviving a bad crash intact.</para>
>        </sect3>
>--- 225,231 ----
>  	  that shifting them more towards the edge of the disk will not
>  	  lead to a significant performance improvement whereas moving
>  	  <filename>/var</filename> to the edge can have a huge impact.
>! 	  Finally, there are safety concerns.  Having a small, neat root
>  	  partition that is essentially read-only gives it a greater
>  	  chance of surviving a bad crash intact.</para>
>        </sect3>
>***************
>*** 282,288 ****
>      </itemizedlist>
>  
>      <para>The <filename>rc.conf.site</filename> file can then be
>!       distributed to every system using <command>rsync</command> or similar
>        program, whilst the <filename>rc.conf</filename> file remains 
>        unique.</para>
>  
>--- 282,288 ----
>      </itemizedlist>
>  
>      <para>The <filename>rc.conf.site</filename> file can then be
>!       distributed to every system using <command>rsync</command> or a similar
>        program, whilst the <filename>rc.conf</filename> file remains 
>        unique.</para>
>  
>***************
>*** 579,584 ****
>--- 579,587 ----
>  nameserver 147.11.1.11
>  nameserver 147.11.100.30</programlisting>
>  
>+ 	<note><para>Only one of the <literal>search</literal> and
>+ 	  <literal>domain</literal> options should be used.</para></note>
>+ 
>  	<para>If you are using DHCP, &man.dhclient.8; usually rewrites 
>  	  <filename>resolv.conf</filename> with information received from the 
>  	  DHCP server.</para>
>***************
>*** 598,604 ****
>  	  a local record of Internet names, reducing the need to query 
>  	  externally for commonly accessed names.</para>
>  
>! 	<programlisting># &dollar;FreeBSD$
>  #
>  # Host Database
>  # This file should contain the addresses and aliases
>--- 601,607 ----
>  	  a local record of Internet names, reducing the need to query 
>  	  externally for commonly accessed names.</para>
>  
>! 	<programlisting># &dollar;FreeBSD&dollar;
>  #
>  # Host Database
>  # This file should contain the addresses and aliases
>***************
>*** 699,706 ****
>  	<indexterm><primary>newsyslog.conf</primary></indexterm>
>  	
>  	<para><filename>newsyslog.conf</filename> is the configuration
>! 	  file for &man.newsyslog.8;, a program that is scheduled to run
>! 	  normally by &man.cron.8;.  &man.newsyslog.8; determines when log
>  	  files require archiving or rearranging.
>  	  <filename>logfile</filename> is moved to
>  	  <filename>logfile.0</filename>, <filename>logfile.0</filename>
>--- 702,709 ----
>  	<indexterm><primary>newsyslog.conf</primary></indexterm>
>  	
>  	<para><filename>newsyslog.conf</filename> is the configuration
>! 	  file for &man.newsyslog.8;, a program that is normally scheduled
>! 	  to run by &man.cron.8;.  &man.newsyslog.8; determines when log
>  	  files require archiving or rearranging.
>  	  <filename>logfile</filename> is moved to
>  	  <filename>logfile.0</filename>, <filename>logfile.0</filename>
>***************
>*** 797,804 ****
>  kern.maxfiles: 2088 -> 5000</screen>
>  
>      <para>Settings of sysctl variables are usually either strings,
>!       numbers, or booleans.  A boolean being <literal>1</literal> for yes
>!       or a <literal>0</literal> for no.</para>
>    </sect1>
>  
>    <sect1 id="configtuning-disk">
>--- 800,807 ----
>  kern.maxfiles: 2088 -> 5000</screen>
>  
>      <para>Settings of sysctl variables are usually either strings,
>!       numbers, or booleans (a  boolean being <literal>1</literal> for yes
>!       or a <literal>0</literal> for no).</para>
>    </sect1>
>  
>    <sect1 id="configtuning-disk">
>***************
>*** 815,821 ****
>  	</indexterm>
>  	
>  	<para>The <varname>vfs.vmiodirenable</varname> sysctl variable
>! 	  defaults to 0 (off) (though soon it will default to 1) and may
>  	  be set to 0 (off) or 1 (on).  This parameter controls how
>  	  directories are cached by the system.  Most directories are
>  	  small and use but a single fragment (typically 1K) in the
>--- 818,824 ----
>  	</indexterm>
>  	
>  	<para>The <varname>vfs.vmiodirenable</varname> sysctl variable
>! 	  defaults to 1 (on) and may
>  	  be set to 0 (off) or 1 (on).  This parameter controls how
>  	  directories are cached by the system.  Most directories are
>  	  small and use but a single fragment (typically 1K) in the
>***************
>*** 884,889 ****
>--- 887,896 ----
>  	it is mounted.  A good time to enable Soft Updates is before any
>  	partitions have been mounted, in single-user mode.</para>
>  
>+       <note><para>As of FreeBSD 4.5, it is possible to enable Soft Updates
>+ 	at filesystem creation time, through use of the <literal>-U</literal>
>+ 	option to &man.newfs.8;.</para></note>
>+ 
>        <para>Soft Updates drastically improves meta-data performance, mainly 
>          file creation and deletion, through the use of a memory cache.  We
>          recommend turning Soft Updates on on all of your filesystems.  There
>***************
>*** 928,948 ****
>  	  kind and number of services running concurrently.</para>
>  
>  	<para><varname>kern.maxfile</varname>'s default value is
>! 	  dictated by the <option>maxusers</option> option in your
>            kernel configuration file.  <varname>kern.maxfiles</varname> grows
>!           proportionally to the value of <option>maxusers</option>.  When
>            compiling a custom kernel, it is a good idea to set this kernel
>            configuration option according to the uses of your system.  From
>            this number, the kernel is given most of its pre-defined limits.
>            Even though a production machine may not actually have 256 users
>            connected as once, the resources needed may be similar to a
>            high-scale webserver.</para>
>        </sect3>
>      </sect2>
>      <sect2>
>        <title>Network Limits</title>
>  
>!       <para>The <varname>NMBCLUSTERS</varname> kernel configuration
>  	option dictates the amount of network mbufs available to the
>  	system.  A heavily-trafficked server with a low number of MBUFs
>  	will hinder FreeBSD's ability.  Each cluster represents
>--- 935,961 ----
>  	  kind and number of services running concurrently.</para>
>  
>  	<para><varname>kern.maxfile</varname>'s default value is
>! 	  dictated by the <option>MAXUSERS</option> option in your
>            kernel configuration file.  <varname>kern.maxfiles</varname> grows
>!           proportionally to the value of <option>MAXUSERS</option>.  When
>            compiling a custom kernel, it is a good idea to set this kernel
>            configuration option according to the uses of your system.  From
>            this number, the kernel is given most of its pre-defined limits.
>            Even though a production machine may not actually have 256 users
>            connected as once, the resources needed may be similar to a
>            high-scale webserver.</para>
>+ 
>+ 	<note><para>As of FreeBSD 4.5, setting <option>MAXUSERS</option> to
>+ 	  <literal>0</literal> in your kernel configuration file will choose
>+ 	  a reasonable default value based on the amount of RAM present in
>+ 	  your system.</para></note>
>+ 
>        </sect3>
>      </sect2>
>      <sect2>
>        <title>Network Limits</title>
>  
>!       <para>The <option>NMBCLUSTERS</option> kernel configuration
>  	option dictates the amount of network mbufs available to the
>  	system.  A heavily-trafficked server with a low number of MBUFs
>  	will hinder FreeBSD's ability.  Each cluster represents

Actions: View | Diff

Attachments on bug 33017: 18350 | 18351