Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=668153 Roy Marples <roy@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roy@xxxxxxxxxxxx --- Comment #8 from Roy Marples <roy@xxxxxxxxxxxx> 2011-02-07 12:58:08 EST --- Hi I'm upstream for openresolv and was asked to comment here, so here I am :) (In reply to comment #2) > Does this work exactly like resolvconf? As far as the user interface is concerned, they are the same as openresolv was designed as a drop in replacement for resolvconf. > We've had no end of problems with > people using resolvconf with NetworkManager, and it's usually fixed by just > removing resolvconf entirely. Ubuntu doesn't even install resolvconf by > default anymore. One of my reasons for writing it :) Good idea but poorly implemented. No doubt in the future someone will do better than me, but until then openresolv is the best at what it does. > How is the final resolv.conf generated and what algorithm defines the priority > of nameservers in the final file? It's entirely user configurable and quite well documented, but the default is pretty much this $configured $dynamic (exclude dynamics with metrics) $metric $sorted $configured is a user defined list, default lo lo[0-9]* $dynamic default is tap[0-9]* tun[0-9]* vpn vpn[0-9]* ppp[0-9]* ippp[0-9]* $metric is numerically ordered and configured by the calling program $sorted is just that So for example, if dhcpcd (which I am also upstream for) works on both wired and wireless interfaces the wired interface would be given a lower metric by default so openresolv would prefer this information. However, this is an extension to how resolvconf works so not much probably uses it other than dhcpcd right now. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review