Date: Mon, 28 May 2012 10:04:30 -0000 From: "Shiv. NK" <prabhpal@digital-infotech.net> To: "Doug Barton" <dougb@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: Named Error Message-ID: <2e74fc890e0faa951358d207d7497e7b.squirrel@mail.digital-infotech.net> In-Reply-To: <4FC34831.2070001@FreeBSD.org> References: <efce1d545da82ba1a97b50700410ed3f.squirrel@mail.digital-infotech.net> <4FC33EEC.4040703@FreeBSD.org> <c85ef9ec8d1d4ca326985504ba991803.squirrel@mail.digital-infotech.net> <4FC34831.2070001@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Dear D. Barton, >> >> thanks for your response, i forgot to tell that the error i reported >> above >> is generated when named is restarted using bash script through cron. >> >> But if i manually restart from terminal window, both commands works just >> fine. without any error > > Then it's definitely a PATH problem. Use the service method described > above and the problem will go away. > > FYI, you almost certainly do not need to restart named via a cron job. > You probably want to write to bind-users@isc.org and describe what > you're trying to accomplish, and they can give you better suggestions on > how to do it. > > Doug Dear D. Barton, thank you very much, you are right, it is $PATH problem. And thank you for your advice. i will do so. Thanks / Regards Nath NK
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2e74fc890e0faa951358d207d7497e7b.squirrel>