On Wed, Jan 09, 2013 at 03:59:51PM +, Tony Finch wrote:
> Chris Thompson wrote:
> > One slight niggling disadvantage is that you can't tell
> > named-checkzone / named-compilezone with the -j option where
> > to find the journal is it isn't in the default location.
>
> I submited a patch to a
Chris Thompson wrote:
>
> One slight niggling disadvantage is that you can't tell
> named-checkzone / named-compilezone with the -j option where
> to find the journal is it isn't in the default location.
I submited a patch to add a -J option which addresses this problem.
(RT #30958)
Tony.
--
f.
On Mon, Jan 07, 2013 at 04:52:53PM +, Chris Thompson wrote:
> On Jan 7 2013, Phil Mayers wrote:
>
> [...]
> >I've never tried it but there's a "journal" option on the zone; maybe
> >this takes paths, like so:
> >
> > zone "foo" {
> >type master;
> ># zone lives outside working dir
>
On Jan 7 2013, Phil Mayers wrote:
[...]
I've never tried it but there's a "journal" option on the zone; maybe
this takes paths, like so:
zone "foo" {
type master;
# zone lives outside working dir
file "/etc/zones/foo";
# ...but journal lives inside it
journal "data/journals/foo
On 07/01/13 14:31, Michael W. Lucas wrote:
Hi,
Running BIND 9.9 on FreeBSD.
named wants to write managed-keys.bind & the journal file in named's
root directory. I can change that with the "directory" option, but
then I have to move all the other directories. Company security policy
is that name
Hi,
Running BIND 9.9 on FreeBSD.
named wants to write managed-keys.bind & the journal file in named's
root directory. I can change that with the "directory" option, but
then I have to move all the other directories. Company security policy
is that named may not do that.
Is there an option that t
6 matches
Mail list logo
