On Sat, 29 Dec 2001 18:02:09 -0800
"Kevin O'Gorman" <[EMAIL PROTECTED]> spewed into the bitstream:
> On Sat, Dec 29, 2001 at 08:23:30PM -0500, [EMAIL PROTECTED] wrote:
> > On December 29, Kevin O'Gorman enlightened our ignorance thusly:
> > > This is very odd.
> > >
> > > My 'named' server won't start from SysV.
> > >
> > > It won't start from a root shell if I try
> > > # cd /etc/rc.d/rc3.d
> > > # ./S10named start
> > >
> > > However, it will start if I do it by sourcing the file:
> > > # . ./S10named start
> >
> > You know, of course, that S10named is just a symlink to
> > /etc/rc.d/init.d/named? What happens if you invoke this script
> > directly? You can also edit it, add "set -x" at the top for debugging
> > output, and then evaluate the differences between the two invocations
> > to see what's going wrong?
> >
> > Kurt
>
> I did that, and it's no where near as helpful as one would hope. For
> one thing, the differences first show up during the sourcing of
> /etc/rc.d/init.d/functions, which is (1) common to pretty much all
> of the SysV files, and (b) not causing problems for any of the others.
>
> For what it's worth, here's the script of both shutdown and startup,
> done both ways. You'll note that I do them in a subshell because
> there's an explicit 'exit' at the end of the script, which otherwise
> messes with me when I source it.
>
[snippage]
do another stop, then start. (the stop to get rid of the .pid file, the
start to try to restart named). Then tail /var/log/messages. You've
probably toasted your named.conf or one of your zone files and named
refuses to start.
If it's not obvious, send it to the list.
Ciao,
David A. Bandel
--
Focus on the dream, not the competition.
-- Nemesis Racing Team motto
Internet (H323) phone: 206.28.187.30
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
