Date: Mon, 5 Feb 2001 19:08:09 +0100 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Broken procfs/status, related to kthreads Message-ID: <20010205190809.A3033@roaming.cacheboy.net> In-Reply-To: <Pine.BSF.4.20.0102050937580.1255-100000@mx.webgiro.com>; from abial@webgiro.com on Mon, Feb 05, 2001 at 09:52:06AM %2B0100 References: <Pine.BSF.4.21.0102050925130.13309-100000@besplex.bde.org> <Pine.BSF.4.20.0102050937580.1255-100000@mx.webgiro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 981361691,37404 0,0 0,5748 select 0 0 0,0 - > > or similar... > > The commands with $ in them are much less likely than the names with > spaces, which on -current are guaranteed to occur. .. or we output information in a new file (say, /proc/$pid/stat?) which looks like the rlimit output? I like that idea better. adrian -- Adrian Chadd "Programming is like sex: <adrian@freebsd.org> One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010205190809.A3033>