| Summary: |
Named not starting during boot. bind-9.3.1-3.2 |
| Product: |
[openSUSE] openSUSE.org
|
Reporter: |
Dieter Jurzitza <dieter.jurzitza> |
| Component: |
Bugzilla | Assignee: |
E-mail List <bnc-team-screening> |
| Status: |
VERIFIED
INVALID
|
QA Contact: |
E-mail List <qa-bugs> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
Keywords: |
Usability |
| Version: |
unspecified | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
32bit | |
|
| OS: |
SuSE Pro 9.3 | |
|
| Whiteboard: |
|
|
Found By:
|
Customer
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
After configuring and testing named (bind) it works flawlessly. During reboot, it is started but somehow stopped again immediatly. Then, after boot, one can call /etc/init.d/named start and everything works fine. I resolved this by entering a delay into /etc/init.d/named: --- named.original 2005-03-19 22:24:12.000000000 +0100 +++ named 2006-02-26 20:19:58.000000000 +0100 @@ -201,6 +201,7 @@ case "$1" in start) + sleep 10 echo -n "Starting name server BIND " checkproc -p ${NAMED_PID} ${NAMED_BIN} case $? in based on the sleep 10 (is heuristical) the boot process is working as expected. Named is running after boot. My assumption: this problem is related to the starting smpppd for the Fritz-Card DSL I am using. When putting the start of named as last entry into the list of started processes (S22named -> ../named in my case) I get the following error message (which surely is related to the problem) Starting name server BIND startproc: signal catched /usr/sbin/named Hangup Whoever or whatever is initiating this.