Thanks again for the help!<div><br></div><div>Very much appreciated!</div><div><br></div><div>JP<br><br><div class="gmail_quote">On Tue, Aug 3, 2010 at 4:49 PM, Perette Barella <span dir="ltr"><<a href="mailto:perette@barella.org">perette@barella.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><br><div><div class="im"><div>On 2010年08月03日, at 18:08, John Puffs wrote:</div><blockquote type="cite">
<div>Seems silly that certain options in the .plist file are not automatically updated. I will file a bug report as this is not good.</div></blockquote></div><div>It may make more sense when you consider that the .plist is *not* dnsmasq's config file. It's a config file for launchd, telling launchd how to invoke dnsmasq. Thus, the way I'd suggest reporting the bug is that the .plist file should not unnecessarily pass dnsmasq parameters that are particulars of dnsmasq configuration.</div>
<div><br></div><div>This way, the automatic update you're envisioning becomes unnecessary. If the .plist doesn't specify -r /etc/resolv.conf at all (because it's not inherently part of launching/managing the process anyway) then it'll use the ones from dnsmasq.conf. So if MacPorts takes these lines out of the .plist:</div>
<div><span style="font-family:monospace"> <string>-r</string></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <string>/etc/resolv.conf</string> (or whatever you've changed it to)</span></div>
<div>and it'll work sensibly. (Which, apparently, is the way I suggested it in the first place: <a href="https://trac.macports.org/ticket/21276" target="_blank">https://trac.macports.org/ticket/21276</a> ... Why they changed it, I don't know.)</div>
<div class="im"><div><br></div><blockquote type="cite"><div>One quick question that I think I know the answer to.. You said "Since command-line options override the config file options in dnsmasq (as with most other utilities), your config file is ignored in preference of the .plist/command line option." I understand that options that are listed in the .plist will override the config file. But do the rest of the config file options still work correctly? </div>
</blockquote><div><br></div></div><div>Yes, the rest of your settings are getting picked up from the .conf file. The -r option (equivalent to "resolv-file" in the config file) is the only option being passed to dnsmasq and thus overriding the resolv-file config file setting. (In a pure sequence-of-operations, dnsmasq IS reading your config file's setting... But then it's overridden by the -r parameter/command line option passed to it.)</div>
<div><br></div><div><br></div><div><br></div><div>And a comment/question on the man page... Under "CONFIG FILE", it indicates:</div><div><div><blockquote type="cite">"For options which may only be specified once, the configuration file overrides the command line."</blockquote>
</div><div><br></div><div>Skimming through I don't see any mention of which ones those are. If any of these still exist, they should be noted somehow.</div><div><br></div><div>Peri</div><div><br></div></div></div></div>
</blockquote></div><br></div>