From: John R. Dennison Sent: November 25, 2009 15:57 > On Wed, Nov 25, 2009 at 03:36:09PM -0800, Hugh E Cruickshank wrote: > > > > That would explain a lot but it would have been more useful if the > > rndc command had returned an error saying something like "start > > command unknown" rather than accepting the command and indicating > > a communication problem. > > It's operating per design and it's operating properly; rndc > is nothing more than an interface to allow admins to provide > commands to the running named instance and if named isn't > running there is nothing that rndc is able to do from that > point forward so it indicates to the user that it can't > communicate - seems logical to me.
I can see that point of view but that sure does not help the poor guy or gal trying to figure out a problem like I had. I have been chasing this one off and on for weeks (if not months). hec -- Hugh E Cruickshank, Forward Software, www.forward-software.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
