Bug 84694 - service named restart does not work correctly
service named restart does not work correctly
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-02-20 12:32 EST by Alessandro Polverini
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-25 15:47:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alessandro Polverini 2003-02-20 12:32:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
I have a caching-only name server on my machine, with only added reverse-ip
mapping for local networks (192.168. and 10.).

If I give the following command:

service named restart

I have this output:

Stopping named:
named: already running[root@japot home]#

If I issue the same command again I get:

Stopping named: rndc: connect failed: connection refused
Starting named:                                            [  OK  ]

So it seems the "service" does not wait enough to shut down bind, before
restarting it.

I tested the same thing on Phoebe beta3 but I have similar results.


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.service named restart

Additional info: none

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