Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Aug 2001 12:44:19 +0100
From:      Josef Karthauser <joe@tao.org.uk>
To:        Robert Watson <rwatson@FreeBSD.ORG>
Cc:        freebsd-fs@FreeBSD.ORG
Subject:   Re: parsing problem with /proc/N/status
Message-ID:  <20010830124419.C5602@tao.org.uk>
In-Reply-To: <20010822083921.A1147@tao.org.uk>; from joe@tao.org.uk on Wed, Aug 22, 2001 at 08:39:21AM %2B0100
References:  <20010817102549.A712@tao.org.uk> <Pine.NEB.3.96L.1010819230616.35655A-100000@fledge.watson.org> <20010822083921.A1147@tao.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help

--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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010830124419.C5602>