From owner-freebsd-current Sun Feb 4 14:37: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7246537B491 for ; Sun, 4 Feb 2001 14:36:44 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id JAA00147; Mon, 5 Feb 2001 09:36:28 +1100 Date: Mon, 5 Feb 2001 09:36:09 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: Broken procfs/status, related to kthreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Feb 2001, Andrzej Bialecki wrote: > According to procfs(5), the status line contains several well-defined > fields separated by spaces. However, the kernel thread names look like > 'swi5: task queue' and 'swi1: net', which results in variable number of > space-separated fields. As a consequence, some software that parses this > line gives incorrect results. I think procfs never actually implemented this. Program names may have spaces in them too. Of course, the line is too hard to parse if the first "field" has spaces in it. Only MAXCOMLEN and NAME_MAX prevent the command name being the contents of another process's status line :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message