commit: 61149280b4421fe4eba6a994c07353587ca97da9
Author: Michael Mair-Keimberger (asterix) gmail
com>
AuthorDate: Wed Jan 18 18:21:41 2017 +
Commit: Alon Bar-Lev gentoo org>
CommitDate: Wed Jan 18 18:42:28 2017 +
URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61149280
ned-dns/openresolv: remove unused file
net-dns/openresolv/files/pdnsd | 673 -
1 file changed, 673 deletions(-)
diff --git a/net-dns/openresolv/files/pdnsd b/net-dns/openresolv/files/pdnsd
deleted file mode 100644
index 7a2d860..
--- a/net-dns/openresolv/files/pdnsd
+++ /dev/null
@@ -1,673 +0,0 @@
-#!/bin/sh
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-# /etc/pdnsd/pdnsd.conf updater
-# Written by Oldrich Jedlicka (oldium@seznam.cz)
-
-# Implementation notes:
-# * The assumptions are same as for other scripts like bind and dnsmasq:
-# - We assume that we are a local dns cache - after all, why would a server
-# use resolvconf?
-# - Now that we have assumed this, we also assume that generic DHCP clients
-# will enter their domains and search domains ONLY in the "search" field
-# in their resolv.confs and VPN clients will put the domain they are for
-# into the domain field only.
-# - This allows pdnsd to forward domains for a specific VPN domain to the
-# VPN nameserver and everything else to the standard name servers.
-#
-# HOW-TO CONFIGURE:
-#
-# To get this working, you need to do only two steps
-#
-# 1. Create a basic configuration of /etc/pdnsd/pdnsd.conf, you can use
-#/etc/pdnsd/pdnsd.conf.example to start.
-#
-#Additional configuration will be created automatically be resolvconf.
-#The generated server sections has labels starting with "resolvconf", so
-#
-#DO NOT USE "resolvconf" IN YOUR LABELS!
-#
-#Check if the status_ctl is set to "on", otherwise the configuration
-#will not be automatically reloaded - see sample config file.
-#
-#You are free to edit automatically created server sections, but always
-#write one option per line. There are few options that are always recreated
-#and your changes in them will be lost. Here is the list (with example
-#values):
-#
-#preset=on;
-#ip="192.168.0.1","192.168.0.2";
-#include=".net",".com";'
-#
-#The exclude directive in "resolvconf" server section is partly recreated.
-#Known (configured) domains in the form "." or ".." are
-#added and removed automatically, unknown domains (also those not in
-#the format above) found in this directive are kept.
-#
-#The sample configuration file /etc/pdnsd/pdnsd.conf prepared to work
-#with resolvconf would look like this:
-#
-#global {
-# perm_cache=2048;
-# run_as="pdnsd";
-# status_ctl = on; # Important to enable status control
-# run_ipv4=on;
-# par_queries=2; # How many servers are probed in parallel
-# interface = "lo"; # Interface on which the pdnsd listens
-#}
-#
-# 2. The last step is to configure dns configuration for /etc/resolv.conf.
-#
-#a) For " or "resolvconf" for global
-# section
-# * @RULE@ is @LABEL@ with translated characters '-' and '.' into '_'.
-###
-
-###
-# Main loop with label match - it will redirect the processing to
-# SED_EDIT_ONE_SERVER, when the label match is found. Special match is
-# for "resolvconf" label - the control flow is redirected to SED_ADDING to
-# allow adding new sections.
-#
-# To summarize: Old sections are edited as they appear in the file and new
-# sections are added before the "resolvconf" section.
-SED_LOOP=\
-'/^[[:space:]]*server[[:space:]]*[\{]/ b server;
-p; d;
-:server; h;
-:server_loop; n;
-/^[[:space:]]*server[[:space:]]*[\{]/ { x; p; b server_loop; };
-@MATCH_LABELS@/^[[:space:]]*label[[:space:]]*=[[:space:]]*"resolvconf"/ { H; b
adding; };
-/^[[:space:]]*[\}]/ { H; x; p; d; };
-H;
-b server_loop;'
-
-###
-# Match for one label with a jump to SED_EDIT_ONE_SERVER
-SED_MATCH_ONE_LABEL=\
-'/^[[:space:]]*label[[:space:]]*=[[:space:]]*"@LABEL@"/ { H; x; b main_@RULE@;
};'
-
-###
-# Editing one server. New lines are put into @SETUP@, lines are composed
-# in function compose_lines(). After the new lines are added, all "preset",
-# "ip" and "include" options are removed (not printed).
-#
-# Sanity checks: Check if there is a second label or another server directive.
-# In both cases, there is some error in the file, so go to the beginning by
-# jumping to SED_LOOP's :server.
-SED_EDIT_ONE_SERVER=\
-':main_@RULE@;
-p; @SETUP@
-:loop_@RULE@;
-n;
-/^[[:space:]]*server[[:space:]]*[\{]/ b server;
-/^[[:space:]]*label[[:space:]]*=/ b server;
-/^[[:space:]]*preset[[:space:]]*=/ b loop_@RULE@;
-/^[[:space:]]*ip[[:space:]]*=/ b loop_@RULE@;
-/^[[:space:]]*include[[:space:]]*=/ b loop_@RULE@;
-/^[[:space:]]*policy[[:space:]]*=/ b loop_@RULE@;
-/^[[:space:]]*exclude[[:space:]]*=/ b
