On Wed, Aug 22, 2001 at 08:39:21AM +0100, Josef Karthauser wrote:
On Sun, Aug 19, 2001 at 11:09:35PM -0400, Robert Watson wrote:
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.
Accepted, but we do support procfs/status as a method too otherwise we
wouldn't implement it.
The procfs manual page says:
status The process status. This file is read-only and returns a single
line containing multiple space-separated fields as follows:
This suggests that whatever we do in addition the minimum is to ensure
that 'command name' doesn't contain spaces. If we're not going to
replace them with underscores, for example, what are we going to replace
Does anyone have a strong opinion on this? If not I'm going to make
this functional change.