From owner-freebsd-ports@FreeBSD.ORG  Mon Feb  7 07:34:01 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CC56516A4CE
	for <ports@FreeBSD.org>; Mon,  7 Feb 2005 07:34:01 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9FEEC43D1D
	for <ports@FreeBSD.org>; Mon,  7 Feb 2005 07:34:01 +0000 (GMT)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 9F5595CA07; Sun,  6 Feb 2005 23:34:01 -0800 (PST)
Date: Sun, 6 Feb 2005 23:34:01 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: Joe Auty <joe@netmusician.org>
Message-ID: <20050207073401.GG95550@elvis.mu.org>
References: <493ef8ebd8d0995079d94e2d106f9222@netmusician.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <493ef8ebd8d0995079d94e2d106f9222@netmusician.org>
User-Agent: Mutt/1.4.2.1i
cc: ports@FreeBSD.org
Subject: Re: FreeBSD Port: mDNSResponder-62_1
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2005 07:34:01 -0000

Can you submit a PR against the port with something that
works for you?  Then tell me the PR.  I'd be happy to commit it.

thank you,
-Alfred

* Joe Auty <joe@netmusician.org> [050204 21:54] wrote:
> Hello,
> 
> I'm not sure if mDNSResponder is used by other ports, but certainly I 
> would assume that a common use is in conjunction with the daapd port?
> 
> Slight problem: the daapd daemon installed from the port runs as user 
> "daapd", and the mdns.sh script provided by this port runs as "nobody". 
> Consequently, the two can't communicate with each and I'm forced to use 
> a home grown rc script.
> 
> Is there anyway this port can be updated to generate a good rc script? 
> Maybe a build menu option? It's a bit of a pain to have to mess around 
> with the rc script to get it to work with daapd everytime I 
> upgrade/reinstall, etc.
> 
> Let me know what you think!
> 
> Thanks in advance for hearing me out, and in all of your work on this 
> port!