On 3/25/22 09:37, The Doctor via bind-users wrote:
On Fri, Mar 25, 2022 at 11:49:54AM +0100, Borja Marcos wrote:
Following up on this subject, looks like there were substantial changes to the
build process for 9.18.1? The port maintainers
seem to be having a hard time with it.
You got that
On 7/30/21 11:13, Ondřej Surý wrote:
> Dennis,
>
> not sure why you are repeating the message you sent to the list before, but
> here’s
> the answer I gave you in May and it is still true:
this --> -print0 and xargs -0 might not be exactly POSIX.1, but
it’s important
While running the testsuite for 9.11.26 on a strict UNIX system I see :
.
.
.
I:autosign: resigned after the active KSK is deleted - stage 2: Verify
that DNSKEY
I:autosign: is now signed with the ZSK. (87)
I:autosign:check that zone with active and inactive ZSK and active KSK
is properly
On 6/17/21 03:47, Manish Rane wrote:
> Does this mean and I can assume that bind has started with 4 cores?
>
> CGroup: /system.slice/named.service
>`-3150 /usr/sbin/named -f -u bind -n 4
> --
> Thanks and
On 5/10/21 01:55, @lbutlr wrote:
> On 06 May 2021, at 09:57, Dennis Clarke via bind-users
> wrote:
>> I do NOT trust a build result where I had to go hacking into all the
>> Makefiles just to get it to build. You install without doing testing?
>
> That's a very strang
On 5/8/21 14:13, Evan Hunt wrote:
> On Thu, May 06, 2021 at 11:57:58AM -0400, Dennis Clarke via bind-users wrote:
>> I do NOT trust a build result where I had to go hacking into all the
>> Makefiles just to get it to build. You install without doing testing?
>
> I think Ondr
On 5/7/21 16:00, Ondřej Surý wrote:
> No, the tests run fine on BSDs, there are no gnuisms.
>
> Solaris just isn’t on our supported platform list
Oh thats right .. you guys dropped it.
Still a whack of legacy boxes out there running but I guess
not ISC Bind in the very very very near future
My test results are a little suspect :
.
.
.
I:ok
I:lwresd:using nosearch.conf
I:ok
I:lwresd:exit status: 0
find: bad option -or
find: [-H | -L] path-list predicate-list
xargs: illegal option -- 0
xargs: find: bad option -print0Usage: xargs: [-t] [-p] [-e[eofstr]] [-E
eofstr] [-I replstr]
On 5/6/21 19:03, Mark Andrews wrote:
> First of all the user running the tests needs to be able to write to
> bin/tests/system. See the permission denied from tee.
>
Well I gave up and decided to run the tests with the same userid and
gid as the acct that created the build.
However I see a
On 5/6/21 19:03, Mark Andrews wrote:
> First of all the user running the tests needs to be able to write to
> bin/tests/system. See the permission denied from tee.
>
I tried that and a pile of *other* things fail :
dude@nix$ ifconfig -a
lo0:6: flags=2001000849 mtu
8232 index 1
inet
I very carefully created an airgap test system for this process and did
setup all the required network interfaces. However all tests fail
terribly due to some weird python requirement ?
airgap$ ./runall.sh -n
+ SYSTEMTESTTOP=.
+ . ./conf.sh
++
On 5/6/21 11:24, Ondřej Surý wrote:
> FTR the test suite is meant to be used by developers. There’s little value to
> use it for validating the production systems.
>
> Generally speaking, having the dependencies and test interfaces (`sudo
> bin/tests/system/ifconfig.sh up`) and running `make
On 5/6/21 10:50, Tony Finch wrote:
> Dennis Clarke via bind-users wrote:
>>
>> Hey there. I looked in the README and I dont see an INSTALL file at all
>> so I have to assume that the testing docs exist somewhere.
>
> Have a look at
>
> https://gitlab.isc.org/i
Hey there. I looked in the README and I dont see an INSTALL file at all
so I have to assume that the testing docs exist somewhere.
I build 9.11.31 after wrangling the Makefile(s) everywhere and now I
have built a separate machine to run the tests. I needed that because
there are a bucket of
On 5/5/21 08:35, Mark Andrews wrote:
> Use a non EoL version of OpenSSL.
>
alpha $ openssl version
OpenSSL 1.1.1k 25 Mar 2021
Not a problem. I have all that sorted out and I did go climb all over
the Makefile in bin/tools and see that it is borked. So I did some
un-bork and now the compile
This has kept me spinning in a few hours since yesterday. So I gave a
try at configure and compile of bind-9.11.31 on ye Fujitsu/Oracle SPARC
Solaris 10 boxen and I see :
.
.
.
/opt/developerstudio12.6/bin/cc -mt
-I/opt/bw/build/bind-9.11.31_sunos5.10_sparcv9.003 -I../..
> And for what it's worth, not all systems moved away from "named" to
> "bind9". I've been running FreeBSD for decades, and I can't remember
> ever calling the service "bind9".
No one ever calls named anything other than named. In a sane world.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
> So as an experienced person who has been doing this you-nuxs thing since
> 1982 - I DON'T see it different - and in fact, I see it as a RETURN to
> what it originally was!
Exactly ! Hear hear ! Well said.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and
On 4/15/20 8:15 AM, Ondřej Surý wrote:
Klaus,
the default and preferred init system on both Debian and Ubuntu is systemd,
and the unit has proper Alias, so it is recognized also under "bind9" name.
The sysv-rc script doesn’t have the capability of aliases, so unfortunately,
there’s
a downfall
On 2020-02-19 16:01, Andreas Hasenack wrote:
Hi,
I didn't find a bind-devel mailing list, so I'm sending this here.
After a plain ./configure && make install, I see in the installed
task.h header file that it includes netmgr.h, but netmgr.h is not
installed. It's not listed in HEADERS in
20 matches
Mail list logo
