Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I realize this is a recurring problem and I want a final resolution to it. I have looked through several similar postings but they haven't completely resolved this issue. I have had this problem for a year. A very similar posting is located at:
LinuxQuestions.org > Forums > Linux - Networking > bind problem
Thread Starter is gubak.
I am using named and rndc. I do not have problems starting up named (/etc/init.d/named start) but my problem occurs when I try to shut it down gracefully using the opposite command (/etc/init.d/named stop). After typing the command, the following output show:
Although it appears to have stopped when I check my /var/log/messages the following output shows after trying to stop named:
app.c:561: unexpected error:
isc_app_shutdown() pthread_kill: No such process
I confirmed that its not running by checking my running processes. Named is still there.
The other major problem is when I use named and rndc commands, I often get the following message:
rndc: connect failed: connection refused
I have not been able, for the life of me, figure out whats wrong. I believe its something with the named script in the /etc/init.d/ folder.
I would really appreciate it if someone could dedicate some attention to my problem. It is of high priority because this is a work related problem.