http://qa.mandrakesoft.com/show_bug.cgi?id=3283
Product: Installation
Component: Installation
Summary: BIND (named) is not / canoot be started - no
/etc/named.conf
Version: 1.807
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This has been working all along (at least until about a week ago), but in
today's cooker the "named" server is not started in my newly installed system.
There is no mention of it in /var/log/syslog. If I start MCC/System/Services,
named shows up as "start on boot". but if I "tail -f /var/log/syslog" and click
on either the Stop or Start buttons, nothing happens: no syslog entry about MCC
issuing a command, and no messages indicating that named is trying to start but
failing.
If I manually try "named -u named", it fails to start because /etc/named.conf
cannot be found.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
