Commit 7beeec88e5f379680abeb4244b0781e102201c0e
Committed by
Jiri Kosina
1 parent
d914e5b703
Exists in
master
and in
7 other branches
docs: fix core_pipe_limit info
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>
Showing 1 changed file with 3 additions and 3 deletions Side-by-side Diff
Documentation/sysctl/kernel.txt
... | ... | @@ -139,9 +139,9 @@ |
139 | 139 | core_pipe_limit: |
140 | 140 | |
141 | 141 | This sysctl is only applicable when core_pattern is configured to pipe core |
142 | -files to user space helper a (when the first character of core_pattern is a '|', | |
142 | +files to a user space helper (when the first character of core_pattern is a '|', | |
143 | 143 | see above). When collecting cores via a pipe to an application, it is |
144 | -occasionally usefull for the collecting application to gather data about the | |
144 | +occasionally useful for the collecting application to gather data about the | |
145 | 145 | crashing process from its /proc/pid directory. In order to do this safely, the |
146 | 146 | kernel must wait for the collecting process to exit, so as not to remove the |
147 | 147 | crashing processes proc files prematurely. This in turn creates the possibility |
... | ... | @@ -152,7 +152,7 @@ |
152 | 152 | processes above that value are noted via the kernel log and their cores are |
153 | 153 | skipped. 0 is a special value, indicating that unlimited processes may be |
154 | 154 | captured in parallel, but that no waiting will take place (i.e. the collecting |
155 | -process is not guaranteed access to /proc/<crahing pid>/). This value defaults | |
155 | +process is not guaranteed access to /proc/<crashing pid>/). This value defaults | |
156 | 156 | to 0. |
157 | 157 | |
158 | 158 | ============================================================== |