Bug 47596

Summary: /sbin/service named start doesn't recognize running copy
Product: [Retired] Red Hat Linux Reporter: John William <jw2357>
Component: bindAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: karl
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-06 07:45:11 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 John William 2001-07-06 07:45:08 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
Running '/sbin/service named start' spawns additional copies of named 
every time the command is run. The new copies recognize (and log 
to /var/messages) that the port is in use, but do not exit - this can fill 
up the machine with processes (and threads on SMP) quickly.

How reproducible:
Always

Steps to Reproduce:
1. run '/sbin/service named start'
2.
3.
	

Actual Results:  Spawns additional copies of named each time the command 
is run (one thread per CPU and per port on which named is listening).

Expected Results:  Should recognize that named is already running and not 
spawn additional programs.

Additional info:

[root@copper RPMS]# rpm -q bind caching-nameserver
bind-9.1.0-10
caching-nameserver-7.1-3

Standard 7.1 system. I marked the bug as normal priority even though it's 
pretty easy to bring down a machine with linuxconf (because it keeps 
starting named).
Comment 1 Bernhard Rosenkraenzer 2001-07-19 10:18:29 UTC 
Fixed in 9.1.3-3
Comment 2 Karl schmidt 2001-07-30 17:39:34 UTC 
I have seen this problem also