docs: fix core_pipe_limit info
PATCH 1/1 docs: fix core_pipe_limit info
From: Randy Dunlap <[email protected]>
Fix typos in core_pipe_limit info.
Signed-off-by Randy Dunlap <[email protected]>
Cc Neil Horman <[email protected]>
--- Documentation/sysctl/kernel.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/sysctl/kernel.txt +3 -3
@@ -139,9 +139,9 @@ core_pattern is used to specify a core d core_pipe_limit: 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 -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 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
@@ -152,7 +152,7 @@ applications in parallel. If this value 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 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. ==============================================================
Jiri Kosina
AppliedQuoted 25 lines · Randy Dunlap
From: Randy Dunlap <[email protected]>
Fix typos in
core_pipe_limitinfo.Signed-off-by Randy Dunlap <[email protected]>Cc Neil Horman <[email protected]>--- Documentation/sysctl/kernel.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/sysctl/kernel.txt +2
-2@@ -139,9 +139,9 @@ core_pattern is used to specify a core d core_pipe_limit: 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 -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 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
Documentation/sysctl/kernel.txt applications in parallel. If this value · line 156
Quoted 6 lines
Documentation/sysctl/kernel.txt +1
-1@@ -152,7 +152,7 @@ applications in parallel. If this value 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 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.
Applied to trivial queue, thanks Randy.
Signature · 2 lines
Jiri Kosina SUSE Labs, Novell Inc.
Quoted 27 lines · Jiri Kosina
Quoted 25 lines · Randy Dunlap
From: Randy Dunlap <[email protected]>
Fix typos in
core_pipe_limitinfo.Signed-off-by Randy Dunlap <[email protected]>Cc Neil Horman <[email protected]>--- Documentation/sysctl/kernel.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/sysctl/kernel.txt +2
-2@@ -139,9 +139,9 @@ core_pattern is used to specify a core d core_pipe_limit: 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 -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 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@@ -152,7 +152,7 @@ applications in parallel. If this value
Quoted 9 lines
Documentation/sysctl/kernel.txt applications in parallel. If this value · line 156
Quoted 6 lines
Documentation/sysctl/kernel.txt +1
-1processes 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 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.Applied to trivial queue, thanks Randy.
Thank you Randy, Jiri.
Neil
Quoted 4 lines
Signature · 2 lines
Jiri Kosina SUSE Labs, Novell Inc.