On Fri May 09 12:42:22 2014, jpopelka@redhat.com wrote: <br />
&gt; This is not really a bug, just a suggestion. <br />
&gt;  <br />
&gt; dhcpd(8) says: <br />
&gt; COMMAND LINE <br />
&gt;         The  names  of  the network interfaces on which dhcpd should  <br />
&gt; listen for broadcasts *may* be specified on the command line.  This  <br />
&gt; should be done on systems where dhcpd is unable to identify  <br />
&gt; non-broadcast interfaces, but *should not be required* on other systems. <br />
&gt;  <br />
&gt; If I don't specify interfaces to listen on, dhcpd listens only on  <br />
&gt; interfaces, for whose it finds subnet declaration in dhcpd.conf. <br />
&gt; For each interface where's no corresponding subnet declaration, dhcpd  <br />
&gt; spits out an *error* <br />
&gt; &quot;No subnet declaration for &lt;interface&gt;. Ignoring requests on  <br />
&gt; &lt;interface&gt;.  If this is not what you want, ...&quot; <br />
&gt; This should not IMHO be an *error*, but only *info*, because there's  <br />
&gt; quite a big chance that this is exactly what user wants. <br />
&gt;  <br />
&gt; If there's no matching subnet declaration for *any* interface dhcpd  <br />
&gt; spits our fatal error <br />
&gt; &quot;Not configured to listen on any interfaces!&quot; <br />
&gt; which is all right. <br />
&gt;  <br />
&gt; With regards, <br />
&gt; Jiri Popelka <br />
&gt; Red Hat, inc. <br />
<br />
I think your suggestion is reasonable, the difficulty is dealing with the historical<br />
inertia of the system. &nbsp;I'm not sure I want to change this from an error in case<br />
people have built that assumption into their systems (nanny scripts and the like).<br />
We shall think about this some more and figure out if there is a clean way to<br />
handle the change.<br />
<br />
Thanks for the suggestion,<br />
Shawn<br />
<br />