Bug 112850
| Summary: | Bind slave grab from other linux distro or win2k-as fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | trinity sabre <trinity> |
| Component: | redhat-config-bind | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | kajtzu, ted.belding |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-01-05 20:56:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
trinity sabre
2004-01-04 02:51:12 UTC
Your bind complains of permissions while creating a temporary file. The bind package owns /var/named/slaves (notice the trailing "s"), not /var/named/slave. Could it be a typo in your configuration? Is your slave directory owned by named:named like below? % ls -ld /var/named/slaves drwxrwx--- 2 named named 4096 Nov 13 02:56 /var/named/slaves If you're running bind as chrooted /var/named/slaves (or /var/named/slave for you?) needs to be located within /var/named/chroot, eg. the path you should be looking for is /var/named/chroot/var/named/slaves. The access permissions still need to be correct. sorry, i meant /var/named/slaves/ (long nyte) ;) the point was more that when installing fedora core, select bind, it installs the chroot dir, and seems to load from it, yet the redhat-config-bind setup doesnt set the correct paths by default for slaves. It creates the slave zones in the correct chrooted dir, but doesnt set the paths correctly. this in turn creates the permission errors until the paths are corrected, i havent tried to reproduce this on any other machines as i am lacking a ps for my test system right now. i will hopefully have a new ps for the test system next week, so, will see if its reproduceable on other hardware... as far as the setup, its /var/named/chroot/var/named/slaves setting the redhat-config-bind generated file to /var/named/slaves/whatever.dom.zone worked fine like i said, more of an annoyance than a bug really, i am not sure if fedora runs bindchrooted by default, but the install i ran set it up by default, so i figured the redhat-config-bind should have worked with the default install if what i typed doesnt make total sense, please bear with me, i'm a windows user and am working on migrating every comp in the office to linux by 2005.... so am learning as i go, some ppl rec'd gentoo but i had some experience with redhat as a desktop environment, and decided to go with something i trusted, plus bugzilla had workarounds for the aic7xxx/i440gx irq issues. heh and have been up now for about 4 days with no sleep making sure everything is working, testing subsystems, and drinking a mad amount of jolt mixed with starbucks doubleshots.. ie, brain has been fried for the last 48 or so hours, hitting bed..... system-config-bind now defaults to the slaves directory. system-config-bind-2.0.2-2 Dan |