ndcerror:cannot connect to command channel?
Barry Margolin
barmar at genuity.net
Thu Jan 25 15:18:26 UTC 2001
In article <94nrjo$906 at pub3.rc.vix.com>, None <None at onon.com> wrote:
>Any have an idea what this means?
It means that named isn't listening for connections on the /etc/ndc socket.
This will happen if named isn't running. I've also seen it after doing
"ndc exec"; for some reason, the new process isn't able to bind to the
socket. Sending a SIGHUP to the named process fixes it.
--
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users
mailing list