Hello,
> Yes, dhclient-script will manage /etc/resolv.conf directly, by
> default.
>
> Now if I were to take the patch suggested by Pierre, I think it's
> going to break dhclient in the instances where it's installed, and no
> other helpers like resolvconf are installed.
Actually no, if the [ -n "$resolv_conf_hook" ] test is false, that is, if no
other helper is installed, dhclient-script will still directly overwrite
/etc/resolv.conf, the default behavior is retained. Nothing should
change until helper hooks are updated.
> Is it possible for this RDNSS daemon you speak of, to integrate it
> with resolvconf instead?
Yes it could and eventually should, but that is beyond the point.
The improvements that this patch makes apply to resolvconf in
the same way.
> If resolvconf is installed, it drops in a hook, which completely
> redefines the make_resolve_conf() function, changing its behaviour.
My patch does two things basically:
- instead of redefining make_resolve_conf(), the hook only has to
set the path to a script, which is both simpler and cleaner
- in my opinion it isn't the job of an external hook to know about
the internals of dhclient functions and variables, and parse them
to write a resolv.conf file: instead of duplicating logic outside of
dhclient-script, my patch makes it output its own resolv.conf file in
/var/run, just like pppd and other do, and handle this file to
resolvconf or whichever hook that needs it
Let me know if you have more questions.
Regards,
--
Pierre Ynard
_____________________________________________________________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
http://mail.yahoo.fr
