From owner-freebsd-fs Sun Aug 19 20: 9:42 2001 Delivered-To: freebsd-fs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9DCEA37B407 for ; Sun, 19 Aug 2001 20:09:39 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f7K39aP35888; Sun, 19 Aug 2001 23:09:36 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 19 Aug 2001 23:09:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Josef Karthauser Cc: freebsd-fs@FreeBSD.ORG Subject: Re: parsing problem with /proc/N/status In-Reply-To: <20010817102549.A712@tao.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I guess my feeling is that fundamentally, this type of process data is "typed" as a nul-terminated string. procfs fails to export all types safely (i.e., unambiguously), including nul-terminated strings. I suppose really, the kernel should export in ASN.1... (run away) Actually, the right answer is probably simply to use sysctl to get this type of process information, since the results actually do have types respected by the medium. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Fri, 17 Aug 2001, Josef Karthauser wrote: > I've raised PR29682 about a problem parsing /proc/N/status (procfs) in > -current. The problem occurs when process names contain spaces, like > all of the 'irqN: xxx' ones do. Is there a procfs guru here that would > mind taking a look for me? > > Many thanks, > Joe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message