will named delete .jnl files ?
Jack Tavares
will eventually get written to the zone files.
My question is:
will named ever delete the .jnl files?
For instance:
updates come in, get stored in .jnl file.
<some time later> those changes are preserved in the zone file.
does named then delete the .jnl file?
My empirical evidence leads me to believe that the answer is "no"
but I certainly haven't tested every possibility.
Thanks
--
Jack Tavares
AIM: jackatavares
SKYPE: jackandkaddee
Reminder: I am at GMT+2, 10 hours AHEAD of Seattle.
My workweek is Sunday-Thursday.
Email sent to me Thursday afternoon (PST) may not be viewed until Sunday morning (GMT+2).
Li Tongxi
file and one .jnl file. And I didn't see the changes preserved in my zone
file. But the DNS works fine and the resolved IP is the updated one not the
one in zone file. Do we need do some config to make the update preserved in
the zone file? I'm using BIND9.3.
2008/10/7 Jack Tavares <j.ta...@f5.com>
Mark Elkins
file, which should probably be followed rapidly with a "rndc <domain>
thaw" command...
Even when the .jnl file is huge - I think that BIND writes out its
concept of the zone from its memory - as a freeze runs very quickly.
I guess the .jnl file is used to replay events to a "named" process that
is restarted??
Would be nice if named did a freeze/thaw cycle on being terminated???
--
. . ___. .__ Posix Systems - Sth Africa. e.164 VOIP ready
/| /| / /__ m...@posix.co.za - Mark J Elkins, Cisco CCIE
/ |/ |ARK \_/ /__ LKINS Tel: +27 12 807 0590 Cell: +27 82 601 0496
David Forrest
> An "rndc <domain> freeze" will consolidate the zone and remove the .jnl
> file, which should probably be followed rapidly with a "rndc <domain>
> thaw" command...
>
> Even when the .jnl file is huge - I think that BIND writes out its
> concept of the zone from its memory - as a freeze runs very quickly.
>
> I guess the .jnl file is used to replay events to a "named" process that
> is restarted??
>
> Would be nice if named did a freeze/thaw cycle on being terminated???
>
I added a couple of lines to my init.d script to do just that. Like this
stop() {
# clean up .jnl files
rndc freeze
rndc thaw
# Stop daemons.
But, since it adds the dynamic changes in force to my original zone file
(and increments the serial number), I found an oddly looking zone file.
Later updates removed the changes and restored the zone file but another
freeze incremented the serial number again.
I finally just left it alone as I was not concerned about the size of the
.jnl files as there is a set *max-journal-size 10K;* (under options).
So I removed that addition from the stop() routine.
David Forrest e-mail drf @ maplepark.com
Maple Park Development Corporation http://www.maplepark.com
St. Louis, Missouri
Chris Thompson
>An "rndc <domain> freeze" will consolidate the zone and remove the .jnl
>file, which should probably be followed rapidly with a "rndc <domain>
>thaw" command...
Yes. But this is not something you should ever need to do in normal
circumstances.
>Even when the .jnl file is huge - I think that BIND writes out its
>concept of the zone from its memory - as a freeze runs very quickly.
It does. It also does this from time to time (c. 15 minues after an
update) during normal running. This does not mean that it clears the
journal file.
To stop the journal file getting out of control, you can use the
"max-journal-size" setting in "options" or "zone" statements.
>I guess the .jnl file is used to replay events to a "named" process that
>is restarted??
The journal file is used not only for replaying updates not yet
committed in the zone file, but also to provide the data for
incremental zone transfers (IXFR).
>Would be nice if named did a freeze/thaw cycle on being terminated???
"rndc stop" (as opposed to "rndc halt") does commit transactions to
the zone file(s). But it doesn't clear the journal files, and nor
should it.
--
Chris Thompson
Email: ce...@cam.ac.uk
Jack Tavares
[quote]
An "rndc <domain> freeze" will consolidate the zone and remove the .jnl
file,
________________________________
From: bind-use...@isc.org on behalf of Mark Elkins
Sent: Tue 10/7/2008 12:03 PM
To: bind-users
Subject: Re: will named delete .jnl files ?
An "rndc <domain> freeze" will consolidate the zone and remove the .jnl
file, which should probably be followed rapidly with a "rndc <domain>
thaw" command...
Even when the .jnl file is huge - I think that BIND writes out its
concept of the zone from its memory - as a freeze runs very quickly.
I guess the .jnl file is used to replay events to a "named" process that
is restarted??
Would be nice if named did a freeze/thaw cycle on being terminated???
On Tue, 2008-10-07 at 17:00 +0800, Li Tongxi wrote:
Mark Elkins
the zone is updated - to what seems like reasonable contents.
This is with respect to a zone used for dynamic updates - and where the
slave is on the same network... so there are no outstanding IXFR's -
which might otherwise keep the .jnl file around.
I guess thats my specuation, observed from (limited?) real(-ish) world
experience and I should have said "may consolidate" rather than "will
consolidate".
Merton Campbell Crockett
records. A dual-boot system that has since been retired left,
roughly, 100 straggling PTR records. I grepped the master zone files
and generated an nsupdate file to remove the straggling PTR records.
After running nsupdate, I executed the following command to update the
master zone file(s) and remove the journal file(s).
rndc freeze zone
I then used the following command to make the zone available.
rndc thaw zone
The name server being used was running BIND 9.3.5-P2.
Merton Campbell Crockett
Merton Campbell Crockett
m.c.cr...@roadrunner.com