Re: detecting resolv.conf changes



Roy Marples wrote:
Howard Chu wrote:
I guess you missed the discussion on this list the first time I posted
this stuff. Writing new resolv.conf files is not a good way to go. You
can pick up on this from the archives if you want.

I'm guessing you have no clue what resolvconf does or how it works as it
addresses the issue first posted in this thread.
You can read about what resolvconf does and how it works in the link I
posted in the last email.

I know what it does. Now please think about system integrity, read-only root filesystems, and needless rewriting of system files, particularly in the context of laptops with hard power constraints. Think about premature wear-out of SSDs caused by repeated overwriting of files. resolvconf is not a good idea.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]