I guess I can use the bind-chroot rpm, ill give that a shot
Thanks, paul
P.A > -----Original Message----- P.A > From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On P.A > Behalf Of Jim Perrin P.A > Sent: Tuesday, February 19, 2008 10:47 AM P.A > To: CentOS mailing list P.A > Subject: Re: [CentOS] named dead but subsys locked P.A > P.A > On Feb 19, 2008 10:42 AM, Paul A razor@meganet.net wrote: P.A > > P.A > > P.A > > P.A > > Hi I recently compliled Bind 9.4.2 on P.A > > P.A > > CentOS release 5 (Final) 2.6.18-53.1.13.el5 #1 SMP P.A > P.A > Why? What's wrong with the bind package that ships with centos? P.A > P.A > > I compiled named chroot, I have done this on several other centos 4 P.A > server P.A > > with no issues however on this centos 5 server im seeing P.A > P.A > > [root@testip1 named]# service named status P.A > > named dead but subsys locked P.A > > [root@testip1 named]# service named stop P.A > > Shutting down named: [FAILED] P.A > P.A > P.A > What init script are you using if you built your own bind? Are you P.A > using selinux on this box? Did you verify the build? P.A > P.A > P.A > > Anyone know what im doing wrong? P.A > P.A > Other than not using rpms? P.A > P.A > Also where can I find the named init script P.A > > for centos 5. P.A > P.A > It's inside the bind package on centos. P.A > P.A > P.A > P.A > -- P.A > During times of universal deceit, telling the truth becomes a P.A > revolutionary act. P.A > George Orwell P.A > _______________________________________________ P.A > CentOS mailing list P.A > CentOS@centos.org P.A > http://lists.centos.org/mailman/listinfo/centos