Re: boot ordering and resolvconf

[Henrique de Moraes Holschuh <hmh@debian.org>]

On Wed, 12 Jun 2013, Wouter Verhelst wrote:
> On 10-06-13 18:36, Ian Jackson wrote:
> > B. resolv.conf is not static and may change due to network
> >    environment changes.
> >     Implications:
> >     1. All existing DNS applications must be modified to notice
> >        changes to resolv.conf.
> >     2. Corollary: all existing DNS resolver libraries must be
> >        so modified.
> >     3. This will be impractical unless a common mechanism with
> >        a convenient interface (and low impact on the rest of a
> >        program) is provided.  Hopefully resolvconf fits this bill.
> > 
> > I don't know exactly how impractical B2 is.  The libc's resolver is
> > probably a hard case because of the libc's low level in the protocol
> > stack.  Can we make it aware of resolvconf ?
> 
> You can replace it (through nsswitch.conf) by lwresd, which can easily
> be restarted when resolv.conf is updated.

I've been using lwresd for a long time (2+ years), and it isn't very
reliable.  I don't think it is widely used at all, we'd need to talk to
upstream about it and probably hit lwresd hard to flush out the worst bugs.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh