From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755018AbZJEWEU (ORCPT ); Mon, 5 Oct 2009 18:04:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754537AbZJEWET (ORCPT ); Mon, 5 Oct 2009 18:04:19 -0400 Received: from cantor2.suse.de ([195.135.220.15]:54069 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754457AbZJEWET (ORCPT ); Mon, 5 Oct 2009 18:04:19 -0400 Date: Tue, 6 Oct 2009 00:03:40 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@wotan.suse.de To: Randy Dunlap Cc: LKML , nhorman@tuxdriver.com Subject: Re: [PATCH trivial] docs: fix core_pipe_limit info In-Reply-To: <4AC95891.3000707@oracle.com> Message-ID: References: <4AC95891.3000707@oracle.com> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 4 Oct 2009, Randy Dunlap wrote: > From: Randy Dunlap > > Fix typos in core_pipe_limit info. > > Signed-off-by: Randy Dunlap > Cc: Neil Horman > --- > Documentation/sysctl/kernel.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > --- linux-next-20090930.orig/Documentation/sysctl/kernel.txt > +++ linux-next-20090930/Documentation/sysctl/kernel.txt > @@ -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//). This value defaults > +process is not guaranteed access to /proc//). This value defaults > to 0. Applied to trivial queue, thanks Randy. -- Jiri Kosina SUSE Labs, Novell Inc.