From owner-freebsd-ports@FreeBSD.ORG  Sun May 15 23:57:06 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0E5D016A4CE
	for <ports@FreeBSD.org>; Sun, 15 May 2005 23:57:06 +0000 (GMT)
Received: from misav02.sasknet.sk.ca (misav02.sasknet.sk.ca [142.165.20.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 58C0D43DC2
	for <ports@FreeBSD.org>; Sun, 15 May 2005 23:57:05 +0000 (GMT)
	(envelope-from shurd@sasktel.net)
Received: from thyme.sasktel.net ([142.165.20.198]) by misav02 with InterScan
	Messaging Security Suite; Sun, 15 May 2005 17:56:59 -0600
Received: from [192.168.0.193]thyme.sasktel.net
	<0IGK0030N2IX5B@thyme.sasktel.net>
	for ports@FreeBSD.org; Sun, 15 May 2005 17:56:59 -0600 (CST)
Date: Sun, 15 May 2005 17:52:52 -0600
From: Stephen Hurd <shurd@sasktel.net>
To: ports@FreeBSD.org
Message-id: <4287E0D4.2070602@sasktel.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-ca, en-gb, en-us, en
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a6) Gecko/20050224
Subject: umask for prog_user su
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2005 23:57:06 -0000

Is there any standard way for an rc.d file which runs as a specific user 
to run with a specific umask?  Putting a umask into the rc.d file has no 
effect, using umask as part of the command (obviously) breaks things.  
If I wanted a umask of 002 during startup for example, what would be the 
correct way to go about this?  Currently, the only solution I've found 
is to write a VERY small wrapper script that just sets the umask then 
execs the binary... it seems a bit silly to me.