Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 14 Jan 2003 15:06:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 14 Jan 2003 15:06:51 -0500 Received: from mark.mielke.cc ([216.209.85.42]:24326 "EHLO mark.mielke.cc") by vger.kernel.org with ESMTP id ; Tue, 14 Jan 2003 15:06:48 -0500 Date: Tue, 14 Jan 2003 15:23:59 -0500 From: Mark Mielke To: "Richard B. Johnson" Cc: DervishD , Linux-kernel Subject: Re: Changing argv[0] under Linux. Message-ID: <20030114202359.GD15412@mark.mielke.cc> References: <20030114195005.GD162@DervishD> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 14, 2003 at 02:56:35PM -0500, Richard B. Johnson wrote: > Well I just grepped through usr/include/bits/posix1_lim.h and it > shows 255 (with this 'C' library) so you are probably right. > In any event, a "whole line of text" isn't going to overrun it. Looking at the code, it looks to me as if argv[0] can be any size up to _SC_ARG_MAX, with the restraining factor being that the environment variables and the other arguments must fit in the same space. Is this not correct? mark -- mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder |\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | | | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada One ring to rule them all, one ring to find them, one ring to bring them all and in the darkness bind them... http://mark.mielke.cc/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/