From owner-freebsd-ports@FreeBSD.ORG Fri Dec 1 16:19:02 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5AEE616A40F for ; Fri, 1 Dec 2006 16:19:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.200.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id C16A443CA7 for ; Fri, 1 Dec 2006 16:18:41 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc14) with ESMTP id <20061201161855014006dmu0e>; Fri, 1 Dec 2006 16:18:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 2D4441FA01D; Fri, 1 Dec 2006 08:18:55 -0800 (PST) Date: Fri, 1 Dec 2006 08:18:55 -0800 From: Jeremy Chadwick To: Bill Moran Message-ID: <20061201161855.GA77647@icarus.home.lan> Mail-Followup-To: Bill Moran , Erik Trulsson , ports@freebsd.org References: <20061130170943.70c02bfe.wmoran@potentialtech.com> <20061130223220.GA6306@owl.midgard.homeip.net> <20061201082756.488cf968.wmoran@potentialtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061201082756.488cf968.wmoran@potentialtech.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: ports@freebsd.org Subject: Re: rsync as a daemon doesn't play nice with rcng X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 16:19:02 -0000 On Fri, Dec 01, 2006 at 08:27:56AM -0500, Bill Moran wrote: > It's odd that there's no command line switch that corresponds. I copied > the rsyncd.conf file from an older system, and didn't look at the sample > until you pointed it out. It would be nice if this could be specified > on the command line, so it could be a default option set in the rc > script. > > Perfect world vs. nearly perfect world ... Consider submitting a bug report to the rsync authors requesting it: http://samba.anu.edu.au/rsync/bugzilla.html I agree that pidfile specification via argv would be useful, but at the same time, rsync has (IMHO) too many command-line options. It makes for an incredibly ugly usage page, makes sifting through the rsync(1) manpage painful, and probably results in quite a mess of code in whatever parses argv. A great example is postgrey; here's our rc.conf entry, which makes me grumble every time I vi rc.conf: postgrey_flags="--pidfile=/var/run/postgrey.pid --inet=10023 -d --user=postgrey --group=postgrey --dbdir=/var/db/postgrey --delay=180 --hostname=mx01.sc1.parodius.com --whitelist-clients=/conf/ME/postfix/postgrey_whitelist_clients --whitelist-recipients=/conf/ME/postfix/postgrey_whitelist_recipients" A configuration file is really where options/tweaks for daemonised things should be kept, with the only command-line arguments supported being very basic things, such as where the configuration file is (ex. -c /foo/bar.conf). :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |