99 lines · plain
1===========================2Documentation for /proc/sys3===========================4 5Copyright (c) 1998, 1999, Rik van Riel <riel@nl.linux.org>6 7------------------------------------------------------------------------------8 9'Why', I hear you ask, 'would anyone even _want_ documentation10for them sysctl files? If anybody really needs it, it's all in11the source...'12 13Well, this documentation is written because some people either14don't know they need to tweak something, or because they don't15have the time or knowledge to read the source code.16 17Furthermore, the programmers who built sysctl have built it to18be actually used, not just for the fun of programming it :-)19 20------------------------------------------------------------------------------21 22Legal blurb:23 24As usual, there are two main things to consider:25 261. you get what you pay for272. it's free28 29The consequences are that I won't guarantee the correctness of30this document, and if you come to me complaining about how you31screwed up your system because of wrong documentation, I won't32feel sorry for you. I might even laugh at you...33 34But of course, if you _do_ manage to screw up your system using35only the sysctl options used in this file, I'd like to hear of36it. Not only to have a great laugh, but also to make sure that37you're the last RTFMing person to screw up.38 39In short, e-mail your suggestions, corrections and / or horror40stories to: <riel@nl.linux.org>41 42Rik van Riel.43 44--------------------------------------------------------------45 46Introduction47============48 49Sysctl is a means of configuring certain aspects of the kernel50at run-time, and the /proc/sys/ directory is there so that you51don't even need special tools to do it!52In fact, there are only four things needed to use these config53facilities:54 55- a running Linux system56- root access57- common sense (this is especially hard to come by these days)58- knowledge of what all those values mean59 60As a quick 'ls /proc/sys' will show, the directory consists of61several (arch-dependent?) subdirs. Each subdir is mainly about62one part of the kernel, so you can do configuration on a piece63by piece basis, or just some 'thematic frobbing'.64 65This documentation is about:66 67=============== ===============================================================68abi/ execution domains & personalities69debug/ <empty>70dev/ device specific information (eg dev/cdrom/info)71fs/ specific filesystems72 filehandle, inode, dentry and quota tuning73 binfmt_misc <Documentation/admin-guide/binfmt-misc.rst>74kernel/ global kernel info / tuning75 miscellaneous stuff76net/ networking stuff, for documentation look in:77 <Documentation/networking/>78proc/ <empty>79sunrpc/ SUN Remote Procedure Call (NFS)80vm/ memory management tuning81 buffer and cache management82user/ Per user per user namespace limits83=============== ===============================================================84 85These are the subdirs I have on my system. There might be more86or other subdirs in another setup. If you see another dir, I'd87really like to hear about it :-)88 89.. toctree::90 :maxdepth: 191 92 abi93 fs94 kernel95 net96 sunrpc97 user98 vm99