From f9979757c38cf8c58408211f77241330fd45f525 Mon Sep 17 00:00:00 2001
From: sjg <sjg@web>
Date: Tue, 12 Jun 2012 10:29:45 -0700
Subject: [PATCH] removed

---
 .../handbook-configtuning-sysctl.mdwn         | 104 ------------------
 1 file changed, 104 deletions(-)
 delete mode 100644 docs/handbook/handbook-configtuning-sysctl.mdwn

diff --git a/docs/handbook/handbook-configtuning-sysctl.mdwn b/docs/handbook/handbook-configtuning-sysctl.mdwn
deleted file mode 100644
index b7faccd6..00000000
--- a/docs/handbook/handbook-configtuning-sysctl.mdwn
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
-## 6.11 Tuning with sysctl 
-
-
-
-[sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8) is an interface that allows you to make changes to a running DragonFly system. This includes many advanced options of the TCP/IP stack and virtual memory system that can dramatically improve performance for an experienced system administrator. Over five hundred system variables can be read and set using [sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8).
-
-
-
-At its core, [sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8) serves two functions: to read and to modify system settings.
-
-
-
-To view all readable variables:
-
-
-
-    
-
-    % sysctl -a
-
-
-
-
-
-To read a particular variable, for example, `kern.maxproc`:
-
-
-
-    
-
-    % sysctl kern.maxproc
-
-    kern.maxproc: 1044
-
-
-
-
-
-To set a particular variable, use the intuitive `***variable***`=`***value***` syntax:
-
-
-
-    
-
-    # sysctl kern.maxfiles=5000
-
-    kern.maxfiles: 2088 -< 5000
-
-
-
-
-
-Settings of sysctl variables are usually either strings, numbers, or booleans (a boolean being `1` for yes or a `0` for no).
-
-
-
-If you want to set automatically some variables each time the machine boots, add them to the `/etc/sysctl.conf` file. For more information see the [sysctl.conf(5)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl.conf&section=5) manual page and the [configtuning-configfiles.html#CONFIGTUNING-SYSCTLCONF Section 6.10.4].
-
-
-
-### 6.11.1 sysctl(8) Read-only 
-
-
-
-***Contributed by Tom Rhodes. ***
-
-
-
-In some cases it may be desirable to modify read-only [sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8) values. While this is not recommended, it is also sometimes unavoidable.
-
-
-
-For instance on some laptop models the [cardbus(4)](http://leaf.dragonflybsd.org/cgi/web-man?command=cardbus&section=4) device will not probe memory ranges, and fail with errors which look similar to:
-
-
-
-    
-
-    cbb0: Could not map register memory
-
-    device_probe_and_attach: cbb0 attach returned 12
-
-
-
-
-
-Cases like the one above usually require the modification of some default [sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8) settings which are set read only. To overcome these situations a user can put [sysctl(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sysctl&section=8) ***OIDs*** in their local `/boot/loader.conf`. Default settings are located in the `/boot/defaults/loader.conf` file.
-
-
-
-Fixing the problem mentioned above would require a user to set `hw.pci.allow_unsupported_io_range=1` in the aforementioned file. Now [cardbus(4)](http://leaf.dragonflybsd.org/cgi/web-man?command=cardbus&section=4) will work properly.
-
-
-
-
-
-
-
-CategoryHandbook
-
-CategoryHandbook-configuration
-
-- 
2.41.0