From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Feb 7 03:00:24 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 B892016A422 for ; Tue, 7 Feb 2006 03:00:24 +0000 (GMT) (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 4AA8A43D45 for ; Tue, 7 Feb 2006 03:00: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 k1730Oxc049003 for ; Tue, 7 Feb 2006 03:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1730OjL049002; Tue, 7 Feb 2006 03:00:24 GMT (envelope-from gnats) Date: Tue, 7 Feb 2006 03:00:24 GMT Message-Id: <200602070300.k1730OjL049002@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Vivek Khera 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: Vivek Khera List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 03:00:24 -0000 The following reply was made to PR ports/92755; it has been noted by GNATS. From: Vivek Khera To: "Jim C. Nasby" Cc: bug-followup@FreeBSD.org Subject: Re: ports/92755: databases/slony1: Add ability to run slon as a different user Date: Mon, 6 Feb 2006 21:53:56 -0500 On Feb 6, 2006, at 6:30 PM, Jim C. Nasby wrote: > I'm sure there's all sorts of better ways to do what I did... feel > free. > :) > > BTW, if you want to get fancy, there's currently nothing in the port > about creating a user account. Might be best to just run under a slony > user by default... Personally I run under the pgsql user and use daemontools to monitor and keep the slon's running. Basically, all you have to do to your patch is whack out the start_slon function and it is just what we need.