Oliver Lehmann wrote:
> Hi Doug,
>
> Doug Barton wrote:
>
>> Your
>> suggestion that I've simply foisted some untested crap onto the
>> FreeBSD community is at best, rude. At worst, it's just plain stupid
>> given that named is chroot'ed by default, and has been for years.
>
> I was not trying t
Hi Doug,
Doug Barton wrote:
> Your
> suggestion that I've simply foisted some untested crap onto the
> FreeBSD community is at best, rude. At worst, it's just plain stupid
> given that named is chroot'ed by default, and has been for years.
I was not trying to blame you in person for anything whi
Oliver Lehmann wrote:
> Did that and used your new script - now it works.
One small thing is left, rndc.key gets always created on start.
There is a typo in line 188+189 of rc.d/named:
if [ -s "${named_confidr}/rndc.key" ]; then
^^^
case `stat
Since you chose to reply to the list rather than to me personally, I
will do the same, although frankly the whole meta-discussion is off
topic, and should be handled privately.
Michal Varga wrote:
> I'm sorry to put it this way, Doug, as I (as many other people around)
> really value the work you
On Fri, Jan 1, 2010 at 8:58 PM, Doug Barton wrote:
> Oliver Lehmann wrote:
>> Hi,
>>
>> since my last RELENG_7 update a new rc.conf variable named_conf appeared.
>>
>> How is this supposted to work with a chroot named? I guess not at all?
>
> I realize that you're frustrated and upset, so I will d
Oliver Lehmann wrote:
> Hi,
>
> since my last RELENG_7 update a new rc.conf variable named_conf appeared.
>
> How is this supposted to work with a chroot named? I guess not at all?
I realize that you're frustrated and upset, so I will disregard the
mildly obnoxious tone of your message, and this
Hi,
since my last RELENG_7 update a new rc.conf variable named_conf appeared.
How is this supposted to work with a chroot named? I guess not at all?
I have in my rc.conf:
named_enable="YES"
named_program="/usr/local/sbin/named"
named_flags="-u bind -c /etc/named/named.conf"
named_chrootdir="/us
