On 26/01/12 11:51, Per Jessen wrote:
lynn wrote:
Error on starting named. rpm -q bind bind-9.8.1P1-4.8.1.i586
/etc/named.conf options { directory "/var/lib/named"; dump-file "/var/log/named_dump.db"; statistics-file "/var/log/named.stats"; listen-on-v6 { any; }; notify no; disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA"; }; zone "." in { type hint; file "root.hint"; }; zone "localhost" in { type master; file "localhost.zone"; }; zone "0.0.127.in-addr.arpa" in { type master; file "127.0.0.zone"; }; include "/etc/named.conf.include";
with /var/lib drwxr-xr-x 9 named named 4096 Jan 26 07:50 named /etc/named.conf.include is empty
What am I doing wrong? Quite likely nothing. I have not looked into why bind complains about the working directory not being writable, but it does not cause a problem for me.
I've yet to see an error free named log without having to intervene manually. If it doesn't need to write to the working directory, then why print the message? named has places under the working directory where it can write. Who does it think it is? Would it at least be possible to lose 'writable';) L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org