From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Sep 22 17:50:25 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org 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 BB3EF16A403 for ; Fri, 22 Sep 2006 17:50:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D85C843D49 for ; Fri, 22 Sep 2006 17:50:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8MHoO0m013411 for ; Fri, 22 Sep 2006 17:50:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8MHoO00013410; Fri, 22 Sep 2006 17:50:24 GMT (envelope-from gnats) Date: Fri, 22 Sep 2006 17:50:24 GMT Message-Id: <200609221750.k8MHoO00013410@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Jim Nasby Cc: Subject: Re: ports/92755: databases/slony1: Add ability to run slon as a different user X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jim Nasby List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 17:50:25 -0000 The following reply was made to PR ports/92755; it has been noted by GNATS. From: Jim Nasby To: bug-followup@FreeBSD.org, Nasby Jim Cc: Subject: Re: ports/92755: databases/slony1: Add ability to run slon as a different user Date: Fri, 22 Sep 2006 13:45:02 -0400 Sorry, I got side-tracked from this (and the email got routed to someplace I don't normally check). > Also, the variable slon_user should be filtered through %%NAME%% > expansion, and might be best located down where the enable flag is > defaulted, too. I guess I'm not clear on this, esp. since I'm defaulting to root? +slon_user=${slon_user:-"root"} > Basically, all you have to do to your patch is whack out the > start_slon function and it is just what we need. I'm not seeing a start_slon function anywhere, so I'm not sure what the intent here is...