This one is a bit of a fun one to understand. Whilst setting this seems to suggest "This will be the biggest size the journal will ever get to", it isn't.
This suggests to bind to flush the journal when it reaches this size. If the journal is busy however, the flush will be delayed until such a time that the journal isn't busy. We use 'max-journal-size 100M;' quite successfully but have seen the journal size get to a few hundred MB. It has stopped multi-GB journal sizes though. Stuart > -----Original Message----- > From: bind-users-boun...@lists.isc.org [mailto:bind-users- > boun...@lists.isc.org] On Behalf Of Bischof, Ralph F. (MSFC-IS40)[NICS] > Sent: Thursday, 12 June 2014 6:00 AM > To: Bind Users Mailing List > Subject: Simple max-journal-size question > > I just can't seem to find the answer to such a simple question (BIND9.9). > > I have a very active dynamic zone that now has an incredibly large journal > file. I would like to use the max-journal-size parameter in the zone > declaration to keep this from happening again. I understand that I can > freeze the zone, delete the journal, and then thaw the zone. My question > deals with when the parameter in the named.conf will take effect. Will an > 'rndc reconfig' be sufficient, or must I stop/start named for the > parameter to be read for the zone? > > Thanks in advance, > RB > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
