On Fri, Jan 27, 2012 at 11:06:33PM +0100, lynn wrote:
On 27/01/12 19:21, Lars Müller wrote: [ 8< ]
Which working directory are you talking about? Please name the path. /var/lib/named
As stated before by security reasons this directory should be owned by user and group root.
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.
Have you tried this? Believe me, this will open your eyes.
After you identified the location the next step is to find a fitting runtime configuration parameter to adjust your config.
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?
Very, very likely not. As I'm eating our own dog food I can proof the default configuration works as expected. The recent update only addressed the handling of the /var/run/named file. I would setup either a separate install in a virtual or chroot environment. Or first look at the output of strace or AppArmor in complain mode. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany