Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Ok, Im trying to get BIND 9.2 to run on my Redhat 7.1 box, and all is working possibly ok except for 1 thing.....
Named starts up just fine from xinetd, no problems at all. however if I kill it and do:
My /var/log/messages reads:
Sep 24 16:23:49 ns3 named: starting BIND 9.2.1
Sep 24 16:23:49 ns3 named: using 1 CPU
Sep 24 16:23:49 ns3 named: loading configuration from '/etc/named.conf'
Sep 24 16:23:49 ns3 named: no IPv6 interfaces found
Sep 24 16:23:49 ns3 named: listening on IPv4 interface lo, 127.0.0.1#53
Sep 24 16:23:49 ns3 named: listening on IPv4 interface eth0, 188.8.131.52#53
Sep 24 16:23:49 ns3 named: command channel listening on 127.0.0.1#953
Sep 24 16:23:49 ns3 named: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 24 16:23:49 ns3 named: exiting (due to early fatal error)
So, I have no idea what to do, I have several other pids in there (ssh, and a few others) but I can't get named to start from the command line-but if i reboot the server it starts up fine. Anyone have any ideas? Im stumped!
Originally posted by morbo What do you mean understand what username? The username is 'named', apparently he doesn't have permission to the named.pid, what should the file permissions be for the named.pid ?
understand why named is running as such, figure out if said usename is in the passwd file, and such
named is probably changing to the user nobody at started. add the -u named to the command will fix that.
I was trying to show him the answer, not tell him.
named.pid should be 600, owned by whatever user you want named to run as (typically named).