NOTICE: This package has been removed from pkgsrc

./wip/openresolv, Framework for managing /etc/resolv.conf

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]

Branch: CURRENT, Version: 2.0, Package name: openresolv-2.0, Maintainer: roy

/etc/resolv.conf is a file that holds the configuration for the local
resolution of domain names. Normally this file is either static or maintained
by a local daemon, normally a DHCP daemon. But what happens if more than one
thing wants to control the file? Say you have wired and wireless interfaces to
different subnets and run a VPN or two on top of that, how do you say which one
controls the file? It's also not as easy as just adding and removing the
nameservers each client knows about as different clients could add the same
nameservers.

Enter resolvconf, the middleman between the network configuration services and
/etc/resolv.conf. resolvconf itself is just a script that stores, removes and
lists a full resolv.conf generated for the interface. It then calls all the
helper scripts it knows about so it can configure the real /etc/resolv.conf
and optionally any local nameservers other can libc.

Master sites:

SHA1: 91cbbcae79686ae2b661e8e2dcf461809e9e200e
RMD160: fdac1ae91c6ee5e36ae809570aae3d3310124b30
Filesize: 8.995 KB

Version history: (Expand)

CVS history: (Expand)


   2008-09-17 15:37:59 by Roy Marples | Files touched by this commit (2) 
Log message:
Bumpage to 1.9
   2008-09-10 14:12:05 by Roy Marples | Files touched by this commit (2) 
Log message:
Bump.
   2008-08-29 10:14:39 by Roy Marples | Files touched by this commit (2) 
Log message:
bump
   2008-08-20 15:33:57 by Roy Marples | Files touched by this commit (2) 
Log message:
Bump to 1.6 - no need for sed at runtime.
   2008-04-07 11:20:36 by Roy Marples | Files touched by this commit (2) 
Log message:
Bump to fix pidfile detection.
   2008-03-07 12:43:05 by Roy Marples | Files touched by this commit (1) 
Log message:
Add PKG_DESTDIR_SUPPORT