From owner-freebsd-fs Thu Aug 30 4:44:28 2001 Delivered-To: freebsd-fs@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id A832F37B40A; Thu, 30 Aug 2001 04:44:20 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 1F7A554A; Thu, 30 Aug 2001 12:44:19 +0100 (BST) Date: Thu, 30 Aug 2001 12:44:19 +0100 From: Josef Karthauser To: Robert Watson Cc: freebsd-fs@FreeBSD.ORG Subject: Re: parsing problem with /proc/N/status Message-ID: <20010830124419.C5602@tao.org.uk> References: <20010817102549.A712@tao.org.uk> <20010822083921.A1147@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xo44VMWPx7vlQ2+2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010822083921.A1147@tao.org.uk>; from joe@tao.org.uk on Wed, Aug 22, 2001 at 08:39:21AM +0100 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --xo44VMWPx7vlQ2+2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: > >=20 > > 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 supp= ose > > really, the kernel should export in ASN.1... (run away)=20 > >=20 > > 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.=20 >=20 > Accepted, but we do support procfs/status as a method too otherwise we > wouldn't implement it. >=20 > The procfs manual page says: >=20 > status The process status. This file is read-only and returns a si= ngle > line containing multiple space-separated fields as follows: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [cut] > 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 > them with? Does anyone have a strong opinion on this? If not I'm going to make this functional change. Joe --xo44VMWPx7vlQ2+2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuOJxIACgkQXVIcjOaxUBZoGQCeNrXyyTP4N6SYhlMsO88JqYOl niMAoKKdo7gODchMKEuF3YeKdbnXF8as =Vby1 -----END PGP SIGNATURE----- --xo44VMWPx7vlQ2+2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message