yep, it has access to the pid file. It creates that one okay, but for
some reason ndc(?) doesn't create the /var/run/ndc file, which I believe
is a pipe of some description.
named actually runs fine. it's just manipulating it via ndc that's the
problem. I wrote my own sb.ndc that does most of the funcitons that I
need, but it would be nice to have the proper ndc working.
any other suggestions?
chris dowling
Robert Glover wrote:
>
> If you're running named as non-root (and you should be),
> then you'll need to make sure it has write access to it's PID file.
>
> > Subject: problem with ndc and named
> > Date: Fri, 14 Jan 2000 14:34:05 +0800
> > From: Chris Dowling <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> >
> > Hi all.
> >
> > when I start named via "ndc start" ndc returns the error:
> > ndc: error: name server has not started (yet?)
> >
> > a ps will show that named is indeed running.
> >
> > further calls to ndc will fail now giving the error message:
> > ndc: error: ctl_client: evConnect(fd 3): Connection refused
> > ndc: error: cannot connect to command channel (/var/run/ndc)
> >
> > nb: /var/run/ndc does not exist.
> >
> > any ideas what is going wrong?
> >
> > TIA,
> > Chris.
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
If a manager offers "constructive advice" and no-one is around to hear
it,
is he still an idiot?
Chris Dowling.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
