Bug 47596 - /sbin/service named start doesn't recognize running copy
/sbin/service named start doesn't recognize running copy
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-06 03:45 EDT by John William
Modified: 2007-04-18 12:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-06 03:45:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John William 2001-07-06 03:45:08 EDT
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 06:18:29 EDT
Fixed in 9.1.3-3
Comment 2 Karl schmidt 2001-07-30 13:39:34 EDT
I have seen this problem also

Note You need to log in before you can comment on or make changes to this bug.