No subject

separate working directory and zones directory. Then all files which
is supposed to be writable will be in working directory (like logs,
statistics files, core files etc) and all others will be in
non-writable directory.

> > Only core files
> > might be problem (it was discussed some time ago) but this is not
> > common situation and admin can explicitly make working directory
> > writable.
> 
> Which does not help with non-(easily)-reproducable conditions.  The
> point in having the directory writable is that you catch the state
> the server is in when you have a problem.
> 
> > > 	If the defaults presented by the OS don't meet the applications
> > > 	needs then the defaults are wrong and should be corrected.
> > > 	"defaults" here covers both the file system and the contents
> > > 	of named.conf.
> > > 
> > > 	Mark
> > 
> > I'm ready to make working directory writable but I don't see any
> > benefit now. Could you point me in which situations named could have
> > problems?
> 
> Failure to write a core is a problem for anyone that wants support.
> Named, deliberately, attempts to write core files.

You are absolutely right.

> 
> Mark
> 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org

Adam

-- 
Adam Tkac, Red Hat, Inc.