From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 7 06:05:32 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2D3016A4D2 for ; Fri, 7 Jan 2005 06:05:32 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43C6843D49 for ; Fri, 7 Jan 2005 06:05:32 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so160592rne for ; Thu, 06 Jan 2005 22:05:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=pqF+6NH5vpyRXoiUOcvW8vaeNuNpegbRXyN57gpCY9+gkQu4seDmm0GSpPNlfwswGPWxNa+WYj2x8v09YifVPi86trYuZr4VaAphzYwDV3LxW2kObgrEeS2NIbX7dUl1xSRLj3bw+hSEI2lq3UGzcchcabSjy1oUJNVsc+9PnyU= Received: by 10.38.11.49 with SMTP id 49mr413683rnk; Thu, 06 Jan 2005 22:05:31 -0800 (PST) Received: by 10.38.89.69 with HTTP; Thu, 6 Jan 2005 22:05:31 -0800 (PST) Message-ID: Date: Thu, 6 Jan 2005 22:05:31 -0800 From: Pascal Hofstee To: "Christian S.J. Peron" In-Reply-To: <20050107051952.A61748@stf01.seccuris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050107051952.A61748@stf01.seccuris.com> cc: Dirk Meyer cc: freebsd-hackers@freebsd.org Subject: Re: GNUstep and libkvm X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pascal Hofstee List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 06:05:32 -0000 On Fri, 7 Jan 2005 05:19:52 +0000, Christian S.J. Peron wrote: > iirc, kvm_getargv() can (and does first) use a sysctl to retrieve > it's data. kvm_getenvv() requires procfs because > /proc//mem is currently the more simpler to read a virtual > memory address in the context of the process. > > We are looking at implementing a similar mechanism to the "argv" > ps_strings for process environment to get rid of the procfs requirement. > > pjd has some work done on this but it has not been committed yet. > Hope this answers your question. Well .. i noticed that kvm_getargv indeed only seems to use /proc in case that apparently the commandline argument list grows beyond a certain size, as i have been able to establish by trial and error. I guess my question is .. is kvm_getargv INTENDED to use the /proc aproach in cases the command + argument list grows beyond a certain size. Because if that IS the case .. the manpage doesn't reflect this. -- With kind regards, Pascal Hofstee