From owner-freebsd-current Mon Feb 5 10: 8:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (node16292.a2000.nl [24.132.98.146]) by hub.freebsd.org (Postfix) with ESMTP id 9101D37B401 for ; Mon, 5 Feb 2001 10:07:49 -0800 (PST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.1/8.11.1) id f15I8AU03130 for freebsd-current@freebsd.org; Mon, 5 Feb 2001 19:08:10 +0100 (CET) (envelope-from adrian) Date: Mon, 5 Feb 2001 19:08:09 +0100 From: Adrian Chadd To: freebsd-current@freebsd.org Subject: Re: Broken procfs/status, related to kthreads Message-ID: <20010205190809.A3033@roaming.cacheboy.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from abial@webgiro.com on Mon, Feb 05, 2001 at 09:52:06AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: 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