Doug Barton a16334d031 In the case where named_chroot_autoupdate is NOT set, but
named_chrootdir IS set, named-checkconf fails because it
cannot find the conf file. Fix this by making checkconf a
variable that includes "-t $named_chrootdir" as needed.
Notice of the bug and suggested direction for the fix from [1].

Using required_files for named.conf is overkill ever since
I added the named-checkconf call, so rather than update the
logic to handle the case described above, remove it. This
also handles the case where named_chroot_autoupdate IS set
but the symlink doesn't exist yet.

PR:		conf/145904
Submitted by:	J R Matthews
2010-04-28 22:29:17 +00:00
..
2009-03-23 00:40:07 +00:00
2009-10-05 09:28:54 +00:00
2006-11-06 01:42:11 +00:00
2010-03-19 15:53:02 +00:00
2009-03-19 12:52:19 +00:00
2009-07-13 05:51:33 +00:00
2006-10-23 05:09:44 +00:00
2006-08-31 21:13:12 +00:00
rc
2008-06-23 04:18:22 +00:00
2010-04-11 15:31:09 +00:00
rpc