Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
09-13-2004, 07:29 PM
|
#1
|
LQ Newbie
Registered: Sep 2004
Location: Oregon
Distribution: RedHat, Mandrake, and Debian
Posts: 11
Rep:
|
why won't named stop??
I'm curious if anyone else has had this problem...
When I try and either restart or stop/start named I get a message that "the service is already running"...
Anyone have any ideas on what causes this and how I can correct it?
Thanks in advance...
Jill
|
|
|
09-13-2004, 09:30 PM
|
#2
|
Member
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321
Rep:
|
It's probably switched on for that runlevel. What do you get from:
'chkconfig --list named'
Last edited by RHELL; 09-13-2004 at 09:31 PM.
|
|
|
09-13-2004, 09:35 PM
|
#3
|
Member
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321
Rep:
|
SORRY, didn't properly read your post. It's giving the same message whether you star/stop/restart.
|
|
|
09-13-2004, 09:50 PM
|
#4
|
LQ Newbie
Registered: Sep 2004
Location: Boston, MA
Distribution: fedora core 2
Posts: 28
Rep:
|
what command line are you using to start/stop/restart?
If you must take down named at all costs use
killall -HUP named
Under normal circumstances I would use
service named stop
(service is a red hat specific command tho, may or may not be available on mandrake)
I think the most likely cause of this, however, is that named isn't actually running, but the thing its init script uses (a pid file) is errantly claiming that it is. The way to see if something is *actually* running would be
ps -ax | grep named
You can also use
netstat -tl
(that's tL) to see what's listening for network connections, though it's possible that named could be running and not listening anywhere (not very likely though).
Last edited by netopia; 09-13-2004 at 09:54 PM.
|
|
|
09-13-2004, 10:22 PM
|
#5
|
Member
Registered: Sep 2004
Location: New Zealand
Distribution: Debian
Posts: 900
Rep:
|
Have a look at the /etc/init.d/named script and see if it's using the presence of a file to determine whether it's running or not. The file would usually be something like /var/run/named.pid
|
|
|
All times are GMT -5. The time now is 05:17 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|