I apologize, I thought I had included you on the changes to this<br />
ticket but see that I didn't do so. &nbsp;<br />
<br />
We have included a patch to address this issue already. &nbsp;It<br />
went into the 4.3 branch and was released as part of 4.3.1b1.<br />
This patch simply allows the DHCP server to continue running<br />
even if the resolver config file can't be read. &nbsp;<br />
<br />
I also passed the issue along to the Bind9 people. &nbsp;I'm not<br />
sure when they will address the issue and depending on<br />
when they address it when that fix will get included with<br />
DHCP as we pull in their libraries.<br />
<br />
regards,<br />
Shawn<br />
<br />
On Fri Jul 18 11:00:40 2014, thozza@redhat.com wrote: <br />
&gt; ----- Original Message ----- <br />
&gt; &gt; I'm sending fixed patch. The code has been moved to <br />
&gt; resconf_parsenameserver() <br />
&gt; &gt; function. <br />
&gt; &gt; <br />
&gt; &gt; ----- Original Message ----- <br />
&gt; &gt; &gt; On 05/13/2014 03:02 PM, Mark Andrews via RT wrote: <br />
&gt; &gt; &gt; &gt; The patch modifies a const char * string. <br />
&gt; &gt; &gt; <br />
&gt; &gt; &gt; Oh, sure, then maybe just move the fix into <br />
&gt; resconf_parsenameserver() ? <br />
&gt; &gt; &gt; I'm sure you'll find something better, it was just a suggestion. <br />
&gt; &gt; &gt; <br />
&gt; &gt; &gt; -- <br />
&gt; &gt; &gt; Jiri <br />
&gt; &gt; &gt; <br />
&gt;  <br />
&gt; Hi. <br />
&gt;  <br />
&gt; We would like to fix this issue in Fedora. We didn't hear anything <br />
&gt; from you <br />
&gt; about this bug since I sent you the fixed patch. <br />
&gt;  <br />
&gt; I would like to ask if there are any problems that we can work out, <br />
&gt; for the patch to be merged? <br />
&gt;  <br />
&gt; Thank you. <br />
&gt;  <br />
&gt; Regards, <br />
<br />
<br />