include order
"Andreas Schwarz" <[email protected]> Wed, 25 Sep 2019 14:15:53 +0200
| Newsgroups | gmane.network.dns.nsd.general |
|---|---|
| Message-ID | <43-5d8b5a80-29-79ae3900@22911000> |
--===============8260961287671603948== Content-Type: multipart/alternative; boundary="----=_=-_OpenGroupware_org_NGMime-67-1569413753.471235-20------" ------=_=-_OpenGroupware_org_NGMime-67-1569413753.471235-20------ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Length: 1093 Hi I am having a strange behavior when using the include directive with gl= obbing. The intention is, to have some "conf.d", where I have my configuration = files. The configuration files are prefixed with a number, e.g. 10-test.conf -> Content "foo" 20-test.conf -> Content "bar" I would expect NSD to include the files in this order. However, restart= ing the service or running nsd-checkconf tells me this: /etc/nsd/conf.d/20-test.conf:1: at 'bar': error: syntax error read /etc/nsd/nsd.conf failed: 1 errors in configuration file I tried several other prefixes (number or letter). It looks like the files are parsed in a somewhat arbitrary order. I can= reproduce this with the NSD packages from several distributions, Debia= n 9, Debian 10, CentOS 7, Arch ... I found this line in the lexer https://github.com/NLnetLabs/nsd/blob/master/configlexer.lex#L124 which to me indicates, that a sorted/predictable outcome for including = files is desired and should work. Is this me doing something wrong? Can anyone else reproduce/explain thi= s behaviour? Best regards Andreas ------=_=-_OpenGroupware_org_NGMime-67-1569413753.471235-20------ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Length: 1261 <html>Hi<br /><br />I am having a strange behavior when using the inclu= de directive with globbing.<br /><br />The intention is, to have some "= conf.d", where I have my configuration files. The configuration files a= re prefixed with a number, e.g.<br /><br />10-test.conf -> Content "= foo"<br />20-test.conf -> Content "bar"<br /><br />I would expect NS= D to include the files in this order. However, restarting the service o= r running nsd-checkconf tells me this:<br /><br />/etc/nsd/conf.d/20-te= st.conf:1: at 'bar': error: syntax error<br />read /etc/nsd/nsd.conf fa= iled: 1 errors in configuration file<br /><br />I tried several other p= refixes (number or letter).<br />It looks like the files are parsed in = a somewhat arbitrary order. I can reproduce this with the NSD packages = from several distributions, Debian 9, Debian 10, CentOS 7, Arch ...<br = /><br />I found this line in the lexer<br />https://github.com/NLnetLab= s/nsd/blob/master/configlexer.lex#L124<br />which to me indicates, that= a sorted/predictable outcome for including files is desired and should= work.<br /><br />Is this me doing something wrong? Can anyone else rep= roduce/explain this behaviour?<br /><br />Best regards<br />Andreas</ht= ml> ------=_=-_OpenGroupware_org_NGMime-67-1569413753.471235-20-------- --===============8260961287671603948== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nsd-users mailing list [email protected] https://open.nlnetlabs.nl/mailman/listinfo/nsd-users --===============8260961287671603948==--