From: Victor Balada Diaz Date: Sun, 17 Sep 2006 19:00:04 +0000 (+0000) Subject: pkgsrc related updates, fix a typo and delete the reference to vfs.vmiodirenable X-Git-Url: https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff_plain/71c86dda9d42d3733df33fcd5af9451a3bb3504c pkgsrc related updates, fix a typo and delete the reference to vfs.vmiodirenable that no longer exists. --- diff --git a/en/books/handbook/config/chapter.sgml b/en/books/handbook/config/chapter.sgml index 41e7d4e0f7..008ee9f49a 100644 --- a/en/books/handbook/config/chapter.sgml +++ b/en/books/handbook/config/chapter.sgml @@ -2,7 +2,7 @@ The FreeBSD Documentation Project $FreeBSD: /usr/local/www/cvsroot/FreeBSD/doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.169 2004/08/27 12:04:24 blackend Exp $ - $DragonFly: doc/en/books/handbook/config/chapter.sgml,v 1.12 2006/07/18 02:02:17 justin Exp $ + $DragonFly: doc/en/books/handbook/config/chapter.sgml,v 1.13 2006/09/17 19:00:04 victor Exp $ --> @@ -289,36 +289,29 @@ system, so that they may be easily located and managed by the package management tools. - /usr/local/etc + /usr/pkg/etc Typically, these files are installed in - /usr/local/etc. In the case where an + /usr/pkg/etc. In the case where an application has a large number of configuration files, a subdirectory will be created to hold them. Normally, when a port or package is installed, sample - configuration files are also installed. These are usually - identified with a .default suffix. If there - are no existing - configuration files for the application, they will be created by - copying the .default files. + configuration files are also installed. These are usually in + /usr/pkg/share/examples/PACKAGENAME. If + there are no existing configuration files for the application, + they will be created by copying the .default + files. For example, consider the contents of the directory - /usr/local/etc/apache: - --rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf --rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf.default --rw-r--r-- 1 root wheel 9555 May 20 1998 httpd.conf --rw-r--r-- 1 root wheel 9555 May 20 1998 httpd.conf.default --rw-r--r-- 1 root wheel 12205 May 20 1998 magic --rw-r--r-- 1 root wheel 12205 May 20 1998 magic.default --rw-r--r-- 1 root wheel 2700 May 20 1998 mime.types --rw-r--r-- 1 root wheel 2700 May 20 1998 mime.types.default --rw-r--r-- 1 root wheel 7980 May 20 1998 srm.conf --rw-r--r-- 1 root wheel 7933 May 20 1998 srm.conf.default - - The file sizes show that only the srm.conf - file has been changed. A later update of the Apache port would not + /usr/pkg/etc/httpd: + +-rw-r--r-- 1 root wheel 43570 Aug 20 15:26 httpd.conf +-rw-r--r-- 1 root wheel 12965 Aug 20 15:26 magic +-rw-r--r-- 1 root wheel 15020 Aug 20 15:26 mime.types + + If you modify any file, for example httpd.conf + a later update of the Apache port would not overwrite this changed file. @@ -332,11 +325,11 @@ These may be started in several different fashions, each having different advantages. - /usr/local/etc/rc.d + /usr/pkg/etc/rc.d Software installed from a port or the packages collection will often place a script in - /usr/local/etc/rc.d which is invoked at + /usr/pkg/etc/rc.d which is invoked at system startup with a argument, and at system shutdown with a argument. This is the recommended way for @@ -348,14 +341,14 @@ when the package is removed. A generic startup script in - /usr/local/etc/rc.d looks like: + /usr/pkg/etc/rc.d looks like: #!/bin/sh echo -n ' FooBar' case "$1" in start) - /usr/local/bin/foobar + /usr/pkg/bin/foobar ;; stop) kill -9 `cat /var/run/foobar.pid` @@ -370,7 +363,7 @@ exit 0 The startup scripts of &os; will look in - /usr/local/etc/rc.d for scripts that have an + /usr/pkg/etc/rc.d for scripts that have an .sh extension and are executable by root. Those scripts that are found are called with an option at startup, and @@ -378,7 +371,7 @@ exit 0 the above sample script to be picked up and run at the proper time during system startup, you should save it to a file called FooBar.sh in - /usr/local/etc/rc.d and make sure it is + /usr/pkg/etc/rc.d and make sure it is executable. You can make a shell script executable with &man.chmod.1; as shown below: @@ -401,7 +394,7 @@ exit 0 Do not place any commands in /etc/rc.conf. To start daemons, or run any commands at boot time, place a script in - /usr/local/etc/rc.d instead. + /usr/pkg/etc/rc.d instead. It is also possible to use the &man.cron.8; daemon to start @@ -967,7 +960,7 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 - Manually configuring the care has the disadvantage that you + Manually configuring the card has the disadvantage that you would have to do it after each reboot of the system. The file /etc/rc.conf is where to add the network card's configuration. @@ -1231,12 +1224,12 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms here. - /usr/local/etc + /usr/pkg/etc Configuration files for installed applications. May contain per-application subdirectories. - /usr/local/etc/rc.d + /usr/pkg/etc/rc.d Start/stop scripts for installed applications. @@ -1484,9 +1477,8 @@ cron.* /var/log/cron running under &os;: kern.logsigexit=0 # Do not log fatal signal exits (e.g. sig 11) -compat.linux.osname=&os; - -compat.linux.osrelease=4.3-STABLE +compat.linux.osname: Linux +compat.linux.osrelease: 2.4.2 @@ -1578,35 +1570,6 @@ device_probe_and_attach: cbb0 attach returned 12 Sysctl Variables - - <varname>vfs.vmiodirenable</varname> - - - vfs.vmiodirenable - - - The vfs.vmiodirenable sysctl variable - may be set to either 0 (off) or 1 (on); it is 1 by default. - This variable controls how directories are cached by the - system. Most directories are small, using just a single - fragment (typically 1 K) in the file system and less - (typically 512 bytes) in the buffer cache. - With this variable turned off (to 0), the buffer - cache will only cache a fixed number of directories even if - ou have a huge amount of memory. When turned on (to 1), this sysctl - allows the buffer cache to use the VM Page Cache to cache the - directories, making all the memory available for caching - directories. However, - the minimum in-core memory used to cache a directory is the - physical page size (typically 4 K) rather than 512  - bytes. We recommend keeping this option on if you are running - any services which manipulate large numbers of files. Such - services can include web caches, large mail systems, and news - systems. Keeping this option on will generally not reduce - performance even with the wasted memory but you should - experiment to find out. - - <varname>vfs.write_behind</varname> @@ -1724,7 +1687,8 @@ device_probe_and_attach: cbb0 attach returned 12 Soft Updates drastically improves meta-data performance, mainly file creation and deletion, through the use of a memory cache. We - recommend to use Soft Updates on all of your file systems. There + recommend to use Soft Updates on all of your file systems but + /. There are two downsides to Soft Updates that you should be aware of: First, Soft Updates guarantees filesystem consistency in the case of a crash but could very easily be several seconds (even a minute!) behind