whereami.conf(5) [debian man page]
whereami.conf(5) File Formats Manual whereami.conf(5) NAME
whereami.conf -- configuration file for whereami DESCRIPTION
The whereami.conf file specifies what whereami does on leaving, remaining at or arriving at locations. (Locations are detected by whereami according to specifications in the detect.conf file.) Comments are lines starting with the `#' character. Leading whitespace is ignored on all lines, including comment lines. Other lines are of the form: -location action The action is performed if your system was previously at this location, but is now at another location. =location action The action is performed if your system is now at this location. +location action The action is performed if your system is now at this location, but was previously at another location. !location action The action is performed if your system is not at this location. HELPER SCRIPTS
In addition to the normal commands available within any shell script, whereami includes a number of helper scripts which may be useful. setmailrelay (none | queue [smarthost] | smarthost) Set the mail relay (i.e. smarthost) to "none" if you have a permanent connection, and can send e-mail directly to the recipient's mailserver. If you are not connected, set the relay to "queue" (optionally for a specific smarthost). Or send all mail to a specific smarthost, if that is what you need in this location. setresolver <resolv.conf stanza> The <resolv.conf stanza> should be something like: search localhost mydomain.com nameserver 1.2.3.4 (all on one line) to specify the domain search path and the nameserver to use. If you have resolvconf installed, this script will interface with that to manupulate the /etc/resolv.conf file and control DNS resolution. This is recommended. If you are not using resolvconf, then this will directly rewrite your /etc/resolv.conf file, inserting a section similar to the manner in which DHCP works. setproxy (start | stop | none | <upstream_proxy>) Use this script to reconfigure your local oops or squid proxy server to use a specific upstream proxy, no upstream proxy, or to stop the proxy server completely. The upstream proxy should be specified as "<name or ip> <port>", e.g.: setproxy 192.168.55.3 3128 For a local squid proxy you can optionally also provide a complete set of parameters for the "cache_peer" directive (without the "cache_peer" name itself). See the squid.conf file for full details of this syntax. e.g.: setproxy 192.168.55.3 parent 3128 3140 login=user:password settimezone timezone Use this to set your timezone differently. masqmail_route route_name Use this to reconfigure masqmail to use a different masqmail routing. SEE ALSO
whereami(8), detect.conf(5) Further documentation is available in the /usr/share/doc/whereami directory. FILES
/etc/whereami/whereami.conf The file we are talking about in this here manpage. /etc/whereami/whereiam.sh The script that is built based on the information in this configuration file and then executed by whereami. LIMITATIONS
There should be a configuration program so that the user does not have to do any script programming. AUTHOR
This manual page was written by Andrew McMillan <debian@mcmillan.net.nz> for the Debian GNU/Linux system (but may be used by others). Per- mission is granted to copy, distribute and/or modify this document under the terms of the GPL version 2. whereami.conf(5)
Check Out this Related Man Page
RESOLVCONF.CONF(5) System Manager's Manual RESOLVCONF.CONF(5) NAME
resolvconf.conf -- resolvconf configuration file DESCRIPTION
resolvconf.conf is the configuration file for resolvconf(8). The resolvconf.conf file is a shell script that is sourced by resolvconf(8), meaning that resolvconf.conf must contain valid shell commands. Listed below are the standard resolvconf.conf variables that may be set. After updating this file, you may wish to run resolvconf -u to apply the new configuration. RESOLVCONF OPTIONS
interface_order These interfaces will always be processed first. If unset, defaults to the following:- lo lo[0-9]* dynamic_order These interfaces will be processed next, unless they have a metric. If unset, defaults to the following:- tap[0-9]* tun[0-9]* vpn vpn[0-9]* ppp[0-9]* ippp[0-9]* search_domains Prepend search domains to the dynamically generated list. search_domains_append Append search domains to the dynamically generated list. domain_blacklist A list of domains to be removed from consideration. To remove a domain, you can use foo.* To remove a sub domain, you can use *.bar name_servers Prepend name servers to the dynamically generated list. You should set this to 127.0.0.1 if you use a local name server other than libc. name_servers_append Append name servers to the dynamically generated list. name_server_blacklist A list of name servers to be removed from consideration. The default is 0.0.0.0 as some faulty routers send it via DHCP. To remove a block, you can use 192.168.* private_interfaces These interfaces name servers will only be queried for the domains listed in their resolv.conf. Useful for VPN domains. This is equivalent to the resolvconf -p option. state_dir Override the default state directory of /run/resolvconf. This should not be changed once resolvconf is in use unless the old direc- tory is copied to the new one. LIBC OPTIONS
The following variables affect resolv.conf(5) directly:- resolv_conf Defaults to /etc/resolv.conf if not set. resolv_conf_options A list of libc resolver options, as specified in resolv.conf(5). resolv_conf_passthrough When set to YES the latest resolv.conf is written to resolv_conf without any alteration. resolv_conf_sortlist A libc resolver sortlist, as specified in resolv.conf(5). resolv_conf_local_only If a local nameserver is configured then the default is just to specify that and ignore all other entries as they will be configured for the local nameserver. Set this to YES to list them instead, if you need working DNS and the local nameserver stops functioning at the expense of duplicated server queries. SUBSCRIBER OPTIONS
openresolv ships with subscribers for the name servers dnsmasq(8), named(8), pdnsd(8) and unbound(8). Each subscriber can create configura- tion files which should be included in in the subscribers main configuration file. dnsmasq_conf This file tells dnsmasq which nameservers to use for specific domains. dnsmasq_resolv This file tells dnsmasq which nameservers to use for global lookups. Example resolvconf.conf for dnsmasq: nameservers=127.0.0.1 dnsmasq_conf=/etc/dnsmasq-conf.conf dnsmasq_resolv=/etc/dnsmasq-resolv.conf Example dnsmasq.conf: listen-address=127.0.0.1 conf-file=/etc/dnsmasq-conf.conf resolv-file=/etc/dnsmasq-resolv.conf named_options Include this file in the named options block. This file tells named which nameservers to use for global lookups. named_zones Include this file in the named global scope, after the options block. This file tells named which nameservers to use for specific domains. Example resolvconf.conf for named: nameservers=127.0.0.1 named_options=/etc/named-options.conf named_zones=/etc/named-zones.conf Example named.conf: options { listen-on { 127.0.0.1; }; include /etc/named-options.conf; }; include /etc/named-zones.conf; pdnsd_conf This is the main pdnsd configuration file which we modify to add our forward domains to. If this variable is not set then we rely on the pdnsd configuration file setup to read pdnsd_resolv as documented below. pdnsd_resolv This file tells pdnsd about global nameservers. If this variable is not set then it's written to pdnsd_conf. Example resolvconf.conf for pdnsd: nameservers=127.0.0.1 pdnsd_conf=/etc/pdnsd.conf # pdnsd_resolv=/etc/pdnsd-resolv.conf Example pdnsd.conf: global { server_ip = 127.0.0.1; status_ctl = on; } server { # A server definition is required, even if emtpy. label="empty"; proxy_only=on; # file="/etc/pdnsd-resolv.conf"; } unbound_conf This file tells unbound about specific and global nameservers. Example resolvconf.conf for unbound: nameservers=127.0.0.1 unbound_conf=/etc/unbound-resolvconf.conf Example unbound.conf: include: /etc/unbound-resolvconf.conf SEE ALSO
resolv.conf(5) and resolvconf(8). AUTHORS
Roy Marples <roy@marples.name> BUGS
Please report them to http://roy.marples.name/projects/openresolv BSD
March 19, 2012 BSD