pkgsrc/net/openresolv/MESSAGE

===========================================================================
$NetBSD: MESSAGE,v 1.4 2009/03/16 21:55:44 roy Exp $

To ensure that resolvconf works correctly, you should ensure that
${PREFIX} is available before any clients attempt to use it.
On NetBSD, for example, you could do this by setting this in /etc/rc.conf
critical_filesystems_local="/usr /var"
and adding ${PREFIX}/sbin to PATH in /etc/rc.conf.

===========================================================================
Satisfy pkglint 2008-12-16 16:49:14 +01:00			`===========================================================================`
Update to openresolv-3.0 No functional changes since 2.x, but the configuration has moved from lots of little configuration files into one easier to manage configuration file with a nice man page - resolvconf.conf 2009-03-16 22:55:44 +01:00			$NetBSD: MESSAGE,v 1.4 2009/03/16 21:55:44 roy Exp $
Satisfy pkglint 2008-12-16 16:49:14 +01:00
/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. 2008-12-16 15:57:58 +01:00			`To ensure that resolvconf works correctly, you should ensure that`
Satisfy pkglint 2008-12-16 16:49:14 +01:00			`${PREFIX} is available before any clients attempt to use it.`
/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. 2008-12-16 15:57:58 +01:00			`On NetBSD, for example, you could do this by setting this in /etc/rc.conf`
			`critical_filesystems_local="/usr /var"`
Update to openresolv-3.0 No functional changes since 2.x, but the configuration has moved from lots of little configuration files into one easier to manage configuration file with a nice man page - resolvconf.conf 2009-03-16 22:55:44 +01:00			`and adding ${PREFIX}/sbin to PATH in /etc/rc.conf.`
Satisfy pkglint 2008-12-16 16:49:14 +01:00
			`===========================================================================`