Date: Sun, 19 Aug 2001 23:09:35 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Josef Karthauser <joe@tao.org.uk> Cc: freebsd-fs@FreeBSD.ORG Subject: Re: parsing problem with /proc/N/status Message-ID: <Pine.NEB.3.96L.1010819230616.35655A-100000@fledge.watson.org> In-Reply-To: <20010817102549.A712@tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010819230616.35655A-100000>