On Mon, 5 Feb 2001, Bruce Evans wrote:
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
In local.freebsd.current you write:
On Mon, 5 Feb 2001, Bruce Evans wrote:
[...]
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
On Mon, Feb 05, 2001, Andrzej Bialecki wrote:
Ok, then how should this be fixed?
We could escape the space characters with something:
swi5:$task$queue 14 0 0 0 -1,-1 noflags 981365276,40 0,0 0,0 nochan 0 0 0,0 -
and for command name 'my$prog':
my$$prog 334 1 332 0 -1,-1 noflags
Hi,
Whoever made procfs aware of kernel threads broke also the
/proc/%pid/status line. Or, maybe it's a by-product of showing
kthreads in the proc table...
According to procfs(5), the status line contains several well-defined
fields separated by spaces. However, the kernel thread names look
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
