Our named.conf is well over 20 meg, so parsing this is quite fun. Can anyone suggest a better method than the one below, which seems to take forever to match towards the end of the file.
The only prerequisites are it has to be bulletproof as named.conf prefers to be error-free (!)
Dev code folows:
local $/=undef;
open(F, "named.conf") || die $!;
my $zonedata=<F>;
close F;
if ($zonedata=~/(zone\s+"$domain"\s+\{\r?\n(.*?)\r?\n(.*?)\r?\n(\s+)?\
+};(\r?\n)+)/) {
print "Got a match on $1\n";
$zonedata=~s/$1//;
#write out..
}
My sole reason for loading into scalar is for simplicity, although I think this is where the problem may be. I avoided
while <> to avoid keeping the file open for longer than was necessary.
FYI a typical entry in named.conf would be:
zone "foobar.com" {
type master;
file "named.foobar.com";
};
Thanks-in-advance Monks
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.