From owner-freebsd-hackers  Wed Jul 14 11: 5:35 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 4B9F114D1C
	for <freebsd-hackers@freebsd.org>; Wed, 14 Jul 1999 11:05:28 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 114TOW-000GYY-00; Wed, 14 Jul 1999 20:04:36 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: wayne@crb-web.com
Cc: Andy Doran <ad@fionn.sports.gov.uk>,
	FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: Re: changing argv[0] after fork() 
In-reply-to: Your message of "Wed, 14 Jul 1999 13:28:07 -0400."
             <Pine.LNX.3.95.990714132715.9360G-100000@crb.crb-web.com> 
Date: Wed, 14 Jul 1999 20:04:36 +0200
Message-ID: <63645.931975476@axl.noc.iafrica.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 14 Jul 1999 13:28:07 -0400, Wayne Cuddy wrote:

> Even though I am developing on FBSD is there a "more portable" way to
> do this?

See the STANDARDS section of the setproctitle(3) manpage. If you worry
that you may port to an operating system whose setproctitle() has a
different calling convention, then stick to manipulating argv[0]. If
your only concern is whether setproctitle() will be present on other
systems, you'll probably want an #ifdef SETPROCTITLE.

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message