Thank you, guys and sorry, I realised how silly my question was when
I'd read docs more carefully.
Now I compiled and installed Knot and trying to feed it with a zone:
# wc -l /srvs/knot/etc/master/example.com
7643502 /srvs/knot/etc/master/example.com
After a few minutes I getting:
# knotc -c /srvs/knot/etc/knot.conf compile
Parsing file '/srvs/knot/etc/master/example.com', origin 'example.com.'
...
error: Compilation of 'example.com.' failed, process was killed.
On the moment of error knot-zcompile occupied about 2 gigs of RAM (of
32) and one CPU core.
With another zone:
# wc -l /srvs/knot/etc/master/example.org
174801 /srvs/knot/etc/master/example.org
all is good.
Both zones contain $TTL and $ORIGIN directives, same SOA record and a
bunch of delegation data with glue records. The main difference is
size of zones.
2012/1/7 Ondřej Surý <ondrej.sury(a)nic.cz>cz>:
Hi,
just install flex from ports.
Ondřej Surý
On 6. 1. 2012, at 20:44, Peter Andreev <andreev.peter(a)gmail.com> wrote:
> Hello, everybody
>
> I tried to compile Knot DNS on FreeBSD 9.0-RC2-amd64, 8.2-amd64,
> 8.2-i386 and everywhere I got ./configure script failed with
>
> checking for reentrant lex... configure: error: could not find lex
> that supports reentrant parsers
>
> Thanks in advance.
>
> --
> --
> AP
> _______________________________________________
> knot-dns-users mailing list
> knot-dns-users(a)lists.nic.cz
>
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
--
--
AP