Bug 6076 - named doesn't start at any runlevel
named doesn't start at any runlevel
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
: 6114 6671 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-10-19 01:49 EDT by tom
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-19 10:47:09 EDT
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 tom 1999-10-19 01:49:24 EDT
Just did a fresh install of RH6.1 on a system.  Named didn't
start automatically, so I started looking around.  In all
rcx.d directories, it was K45named.  Under a RH6.0 install I
did on another system, it was S55named in rc3.d, rc4.d and

I renamed the files to match my RH6.0 install, and all looks
Comment 1 Bill Nottingham 1999-10-19 10:47:59 EDT
It's a change in policy. You can use ntsysv, or
chkconfig --level 345 named on
to turn it on.
Comment 2 Bill Nottingham 1999-10-20 00:14:59 EDT
*** Bug 6114 has been marked as a duplicate of this bug. ***

When upgrading from RH 6.0 to RH 6.1...
The next thing I noticed is that my DNS (named) was no
longer running.  To fix this rename the "K45named" file in
rc3.d, rc4.d, and rc5.d to "S55named".  And then issue the
following command:

/etc/rc.d/init.d/named start
Comment 3 Bill Nottingham 1999-11-03 12:07:59 EST
*** Bug 6671 has been marked as a duplicate of this bug. ***

NFS start moved to init 4 from init 3 in RH 5.2

Why all these policy changes? named doesn't even start in
RH6.1 unless manual tweaking is done! Yuk!

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