From owner-freebsd-questions Mon Jul 22 12:39:30 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00198 for questions-outgoing; Mon, 22 Jul 1996 12:39:30 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00192 for ; Mon, 22 Jul 1996 12:39:28 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA21664; Mon, 22 Jul 1996 13:39:12 -0600 (MDT) Date: Mon, 22 Jul 1996 13:39:12 -0600 (MDT) Message-Id: <199607221939.NAA21664@rocky.mt.sri.com> From: Nate Williams To: "Mark O'Lear" Cc: questions@freebsd.org Subject: Re: gmake 3.74 port setgid kmem In-Reply-To: <31F3D43D.5F2C@Colorado.EDU> References: <31F3D43D.5F2C@Colorado.EDU> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone know if the gmake 3.74 port (in ports-current) is > supposed to leave gmake with setgid kmem? The gmake package > in packages-current does this as well. Yes, it's supposed do. > If this is standard behavior for gmake, why does it > need to be (and why kmem)? If it needs to be, why does > regular make work just fine without it? One of the 'features' of gmake is the ability to 'stop compiling' until the load average of the machine goes down to an acceptable level, so it needs permissions to read /dev/mem to determine the load average. I consider it's setgid-ness along with the 'load average' bit to be a mis-feature. Nate