Hello all,
ijust have installed a new server freebsd 7.2 -RELEASE -p4
and after the base-install i patched with the command freebsd-update fetch, freebsd-install .....reboot the server .
Everything went fine for so far till i installed bind96 (bind96-base-9.6.11) via the portscollection. I used the portsnap fetch command (portsnap extract etc)
During the installation i didn't saw anny wrong warnings.
But after when i made the zonefiles example.com and example.com.rev and also added the rule named_enabled="YES" in /etc/rc.conf and also added the rule NO_BIND=YES in /etc/make.conf i saw during the reboot a warning rule called
"named[689]: the working directory is not writable
i logged in became root and patched again with the command:
freebsd-update fetc, freebsd-update install and rebooted again the server.
Still the same warning like above,...the working directory is not writable.
I googled but didn't find for so far.
Can anyone tell me what to do to make this problem solved
I did the same with an other freebsd 7.1 RELEASE also with bind96 and patched it and after reboot the problem solved.
Howe is this possible that the newer release 7.2 p4 still have the problem with bind96 .6.1.1
Before i installed Bind96, i used the portaudit -f command to be shore that there are no Vulnerbilities.
I am looking forward to the answers
greets,
beastie_007 ;-)
ijust have installed a new server freebsd 7.2 -RELEASE -p4
and after the base-install i patched with the command freebsd-update fetch, freebsd-install .....reboot the server .
Everything went fine for so far till i installed bind96 (bind96-base-9.6.11) via the portscollection. I used the portsnap fetch command (portsnap extract etc)
During the installation i didn't saw anny wrong warnings.
But after when i made the zonefiles example.com and example.com.rev and also added the rule named_enabled="YES" in /etc/rc.conf and also added the rule NO_BIND=YES in /etc/make.conf i saw during the reboot a warning rule called
"named[689]: the working directory is not writable
i logged in became root and patched again with the command:
freebsd-update fetc, freebsd-update install and rebooted again the server.
Still the same warning like above,...the working directory is not writable.
I googled but didn't find for so far.
Can anyone tell me what to do to make this problem solved
I did the same with an other freebsd 7.1 RELEASE also with bind96 and patched it and after reboot the problem solved.
Howe is this possible that the newer release 7.2 p4 still have the problem with bind96 .6.1.1
Before i installed Bind96, i used the portaudit -f command to be shore that there are no Vulnerbilities.
I am looking forward to the answers
greets,
beastie_007 ;-)