Minki/linux
1
0
Fork 1
mirror of https://github.com/torvalds/linux.git synced 2024-12-31 23:31:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix core_pipe_limit info

Browse Source 
Fix typos in core_pipe_limit info.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
Randy Dunlap 2009-10-04 19:23:13 -07:00 committed by Jiri Kosina
parent d914e5b703
commit 7beeec88e5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/sysctl/kernel.txt
View File

@ -139,9 +139,9 @@ core_pattern is used to specify a core dumpfile pattern name.
core_pipe_limit: core_pipe_limit:
This sysctl is only applicable when core_pattern is configured to pipe core This sysctl is only applicable when core_pattern is configured to pipe core
files to user space helper a (when the first character of core_pattern is a '|', files to a user space helper (when the first character of core_pattern is a '|',
see above). When collecting cores via a pipe to an application, it is see above). When collecting cores via a pipe to an application, it is
occasionally usefull for the collecting application to gather data about the occasionally useful for the collecting application to gather data about the
crashing process from its /proc/pid directory. In order to do this safely, the crashing process from its /proc/pid directory. In order to do this safely, the
kernel must wait for the collecting process to exit, so as not to remove the kernel must wait for the collecting process to exit, so as not to remove the
crashing processes proc files prematurely. This in turn creates the possibility crashing processes proc files prematurely. This in turn creates the possibility
@ -152,7 +152,7 @@ applications in parallel. If this value is exceeded, then those crashing
processes above that value are noted via the kernel log and their cores are processes above that value are noted via the kernel log and their cores are
skipped. 0 is a special value, indicating that unlimited processes may be skipped. 0 is a special value, indicating that unlimited processes may be
captured in parallel, but that no waiting will take place (i.e. the collecting captured in parallel, but that no waiting will take place (i.e. the collecting
process is not guaranteed access to /proc/<crahing pid>/). This value defaults process is not guaranteed access to /proc/<crashing pid>/). This value defaults
to 0. to 0.
============================================================== ==============================================================