From owner-freebsd-ports-bugs@FreeBSD.ORG Fri May 16 06:30:14 2003 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6C5037B401 for ; Fri, 16 May 2003 06:30:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4958F43F3F for ; Fri, 16 May 2003 06:30:14 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4GDUEUp043205 for ; Fri, 16 May 2003 06:30:14 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4GDUEFZ043203; Fri, 16 May 2003 06:30:14 -0700 (PDT) Date: Fri, 16 May 2003 06:30:14 -0700 (PDT) Message-Id: <200305161330.h4GDUEFZ043203@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Bob Van Valzah Subject: Re: ports/51548: cfexecd from cfengine2 port has wrong path to cfagent X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bob Van Valzah List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 13:30:15 -0000 The following reply was made to PR ports/51548; it has been noted by GNATS. From: Bob Van Valzah To: freebsd-gnats-submit@FreeBSD.org Cc: bob@Bastion.VanValzah.Com Subject: Re: ports/51548: cfexecd from cfengine2 port has wrong path to cfagent Date: Fri, 16 May 2003 08:23:08 -0500 (CDT) Please close this PR--I never should've opened it. At the time, I didn't understand what cfengine2 was trying to do. Now I think I do. I'm not at all sure I agree with it, but I understand it. I now believe it is correct for the port to install everything under /usr/local and for cfengine to have hard-wired paths expecting to run it from /var/cfengine/bin. Common practice seems to be to write cfengine scripts that copy the binaries you want to run either from a local source (e.g. /usr/local/sbin) or a trusted policy host into /var/cfeingine/bin. I can't find mention of this expectation in the docs, but the usage examples all go this way and it kinda makes sense. I've also just submitted a port upgrade to version 2.0.6. Sorry to've troubled you with this. Bob