9 messages in org.freebsd.freebsd-fsRe: parsing problem with /proc/N/status| From | Sent On | Attachments |
|---|---|---|
| Josef Karthauser | Aug 17, 2001 2:25 am | |
| Dag-Erling Smorgrav | Aug 17, 2001 3:13 pm | |
| Josef Karthauser | Aug 18, 2001 6:19 am | |
| Arne Dag Fidjestøl | Aug 18, 2001 4:23 pm | |
| Dan Ellard | Aug 18, 2001 5:49 pm | |
| Dag-Erling Smorgrav | Aug 18, 2001 7:14 pm | |
| Robert Watson | Aug 19, 2001 8:09 pm | |
| Josef Karthauser | Aug 22, 2001 12:38 am | |
| Josef Karthauser | Aug 30, 2001 4:43 am |
| Subject: | Re: parsing problem with /proc/N/status | |
|---|---|---|
| From: | Robert Watson (rwat...@FreeBSD.ORG) | |
| Date: | Aug 19, 2001 8:09:13 pm | |
| List: | org.freebsd.freebsd-fs | |
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 rob...@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 majo...@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message