Re: [CFR] reflect resolv.conf update to running application

From: Matthew N. Dodd (mdodd_at_FreeBSD.ORG)
Date: 09/15/05

  • Next message: Xin LI: "Combine more operation within one system call: to do it, or not to do it?" 
    Date: Thu, 15 Sep 2005 09:59:48 -0400 (EDT)
To: Doug Barton <dougb@FreeBSD.ORG>

    On Thu, 15 Sep 2005, Doug Barton wrote:
    > Yes, include works, but it runs a similar risk to modifying the
    > named.conf file, namely if the syntax of the the statements in the
    > include file are not right, loading named.conf will fail. So, we should
    > build some caution into the process of updating the file, but that's
    > easily done with the named-checkconf program that comes with the
    > distribution.

    I'm not sure such paranoia is needed; dhclient has always exposed the
    system to the risk of having an invalid resolv.conf and regenerating the
    named.conf file is no different. Since we're regenerating the included
    file completely I don't see that this is risky at all.

    >> + rm -f ${dhclient_script_forwarders_file}.$$
    >> + echo " forward only;" > ${dhclient_script_forwarders_file}.$$
    >
    > This should really be 'forward first'. That configuration is less likely to
    > fail in weird, and hard to diagnose ways.

    I don't agree. I've run into networks that block recursive queries for
    everything but the published nameserver. There wouldn't be a need for
    this frobbing if we could just make recursive queries directly.

    > if named-checkconf /etc/namedb/named.conf; then
    > rndc reconfig
    > fi

    This check seems reasonable. 

    -- 
10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Xin LI: "Combine more operation within one system call: to do it, or not to do it?"

    Relevant Pages

    • Re: generalizations
      ... To fail to make that effort is to risk being bigots in the ...
      (soc.atheism)
    • Re: Nationalized Health Care Preview?
      ... employees to taxpayers. ... better that the risk be assumed by those who had had the option ... that they fail. ... amount of active intervention is required. ...
      (rec.arts.sf.fandom)
    • Re: a self deleting program
      ... it's very likely to fail. ... Windows shutdown is very good at killing off ... That's the risk you run if you implement poor solutions like this!!! ... Should this happen it will give your app an *extremely* ...
      (microsoft.public.vb.general.discussion)
    • Re: [CFR] reflect resolv.conf update to running application
      ... namely if the syntax of the the statements in the ... > I'm not sure such paranoia is needed; dhclient has always exposed the ... > system to the risk of having an invalid resolv.conf and regenerating the ... Since we're regenerating the included ...
      (freebsd-arch)
    • Re: RSVP (and pinatas)
      ... There might be a theoretical risk, but IME, it doesn't bear out. ... when it comes to this sort of thing. ... their kids to schools around here that don't have directories. ... I think it's easy to fail to consider the possibility that the ...
      (misc.kids)