On 27/01/12 19:21, Lars Müller wrote:
On Fri, Jan 27, 2012 at 06:49:58PM +0100, lynn wrote: [ 8< ]
Still no luck: /etc/named.conf options { directory "/var/lib/named"; managed-keys-directory "/var/lib/named/dyn/"; #dump-file "/var/log/named_dump.db"; #statistics-file "/var/log/named.stats"; produces: Jan 27 18:34:36 hh3 named[2547]: the working directory is not writable
Yast SysConfig was used to change named to non-chroot No further comment. You know it better anyway. :)
ls -la /var drwxr-xr-x 12 root root 4096 Jan 27 18:28 log
The only way I can fix it is to change the working directory to named:named :( Which working directory are you talking about? Please name the path. /var/lib/named
/var/log must not be owned by named. ls -la /var drwxr-xr-x 12 root root 4096 Jan 27 18:28 log
It looks like your bind configuration leads to more write attempts at different locations than in the default configuration case.
Either use AppArmor in complain mode to see what's going on or follow the daemon with strace for example.
After you identified the location the next step is to find a fitting runtime configuration parameter to adjust your config.
Cheers,
Lars
The only thing not default about this configuration is the non chroot. Everything else is as it comes as of last update. Does changing to non chroot cause this error? Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org