X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@lists.alpinelinux.org
Received: from mail.squbes.com (squbes.com [208.74.142.49])
	by lists.alpinelinux.org (Postfix) with ESMTP id A60FB360F717
	for <alpine-devel@lists.alpinelinux.org>; Sun, 15 Nov 2009 05:51:47 +0000 (UTC)
Received: from [10.252.6.134] (c-98-234-19-2.hsd1.ca.comcast.net [98.234.19.2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: nangel@nothome.org)
	by mail.squbes.com (Postfix) with ESMTPSA id 5A3A550001CAD;
	Sun, 15 Nov 2009 05:51:46 +0000 (UTC)
Message-ID: <4AFF96CC.6070502@nothome.org>
Date: Sat, 14 Nov 2009 21:51:08 -0800
From: Nathan Angelacos <nangel@nothome.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
To: MarkSeymour@GuildAssociates.com
CC: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel]  how do I get axfrdns (djbdns) going in Alpine?
References: <9BDC6D38983C45A6A0710925FF6BDE50@markseymour> <4AFE6935.3090500@iki.fi> <91FB85D6D06D447EACD6081220834F24@markseymour>
In-Reply-To: <91FB85D6D06D447EACD6081220834F24@markseymour>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable

Mark,

Thanks for your kind words and interest in AlpineLinux.


MarkSeymour@GuildAssociates.com wrote:
> On Saturday, November 14, 2009 "Timo Ter=E4s" timo.teras@iki.fi wrote:
>>
>> I have axfrdns running on an Alpine 1.8 based box. It uses tcpserver from
>> ucspi-tcp package. I attached the init.d script I'm using. Something like
>> this should be added to djbdns package.
>>
>=20
> Thanks to Timo for the reply and for the init.d script.  I guess I will=20
> grab the
> 1.8.3 iso,  and use it for now as 1.9.1 iso does not have ucspi-tcp.

Yeah.  ucspi-tcp was in 1.8.3  I've gone ahead and made a feature=20
request in your behalf:

http://redmine.alpinelinux.org/issues/show/206

Generally these things take a few days to happen, so if you can wait a=20
few days, I'd recommend waiting.  1.9.x is /much/ better than 1.8.x, in=20
a number of ways.

Going back is kinda like driving a BMW M3 and then moving to a Toyota=20
corolla.  It will work... but...

FWIW, 1.9 packages have been more along the lines of "who actually asks=20
for XXX than 'hey ... XXX is cool, let's add it"  Since you have asked=20
for it, that tells us there's a need.

>=20
> In order to control which slaves are allowed, where do you put your
>    '<slaveIP>:allow,AXFR=3D"<allowedAXFRDomain>"'
> entries which, under Bernstein's regime, go in a file that normally lives
> at /etc/axfrdns/tcp ?
>=20
> Although I see that the axfrdns-conf program exists in the djbdns apk,
> I assume that I should not use it to set up axfrdns, as multilog  is not =

> available
> since there is no daemontools package.

Daemontools is a  good idea, especially for multilog; here's that=20
feature request:

http://redmine.alpinelinux.org/issues/show/205

I run tinydns / dnscache on multiple production domains, having logging=20
*would* be handy :-)

>=20
> Seems  'lbu ci usb' does not retain changes made in /etc/init.d, so I=20
> should add
> a reference to the axfr start script in  /etc/lbu/include , correct?

Try, and let us know if it works.

I believe you stumbled into a "feature" of the 1.9 lbu.   its about 100x=20
faster than 1.8, but currently doesn't back up certain files under=20
special circumstances.  This might be one of them.

If so, it needs to be fixed.

>=20
> Any chance someone would package up daemontools for Alpine and just
> allow this to be set up the way that DJB intends, including svc, svscan,
> multilog, etc?  (Is there a strong reason not to do this?)
>=20

Yeah, we'll try to get daemontools packaged.  That way you can use it=20
the way DJB intends.

As far as reasons not to... I'm sure you've run into it before...=20
everything is /etc/init.d/[service] start|stop *except* djb stuff.  I've=20
never gotten used to that.

Alpine 1.8 uses scripts in /etc/rc.d;  1.9 uses open-rc [rc-service=20
dnscache start].  Just to keep my sanity, I'd rather spend the time to=20
write a service script for you (and the distro) than remember "djb stuff=20
is different"

YMMV






---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---