<?xml version="1.0" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Smokeping/probes/AnotherDNS</title> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <link rev="made" href="mailto:root@localhost" /> </head> <body style="background-color: white"> <p><a name="__index__"></a></p> <!-- INDEX BEGIN --> <!-- <ul> <li><a href="#name">NAME</a></li> <li><a href="#synopsis">SYNOPSIS</a></li> <li><a href="#description">DESCRIPTION</a></li> <li><a href="#variables">VARIABLES</a></li> <li><a href="#authors">AUTHORS</a></li> </ul> --> <!-- INDEX END --> <p> </p> <h1><a name="name">NAME</a></h1> <p>Smokeping::probes::AnotherDNS - Alternate DNS Probe</p> <p> </p> <hr /> <h1><a name="synopsis">SYNOPSIS</a></h1> <pre> *** Probes ***</pre> <pre> +AnotherDNS</pre> <pre> forks = 5 offset = 50% step = 300</pre> <pre> # The following variables can be overridden in each target section lookup = www.example.org mininterval = 0.5 pings = 5 port = 53 recordtype = A require_answers = 0 require_noerror = 0 timeout = 5</pre> <pre> # [...]</pre> <pre> *** Targets ***</pre> <pre> probe = AnotherDNS # if this should be the default probe</pre> <pre> # [...]</pre> <pre> + mytarget # probe = AnotherDNS # if the default probe is something else host = my.host lookup = www.example.org mininterval = 0.5 pings = 5 port = 53 recordtype = A require_answers = 0 require_noerror = 0 timeout = 5</pre> <p> </p> <hr /> <h1><a name="description">DESCRIPTION</a></h1> <p>Like DNS, but uses Net::DNS and Time::HiRes instead of dig. This probe does *not* retry the request three times before it is considerd ``lost'', like dig and other resolver do by default. If operating as caching Nameserver, BIND (and maybe others) expect clients to retry the request if the answer is not in the cache. So, ask the nameserver for something that he is authoritative for if you want measure the network packet loss correctly.</p> <p>If you have a really fast network and nameserver, you will notice that this probe reports the query time in microsecond resolution. :-)</p> <p> </p> <hr /> <h1><a name="variables">VARIABLES</a></h1> <p>Supported probe-specific variables:</p> <dl> <dt><strong><a name="item_forks">forks</a></strong> </dt><dd> <p>Run this many concurrent processes at maximum</p> <p>Example value: 5</p> <p>Default value: 5</p> </dd><dt><strong><a name="item_offset">offset</a></strong> </dt><dd> <p>If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.)</p> <p>Example value: 50%</p> </dd><dt><strong><a name="item_step">step</a></strong> </dt><dd> <p>Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.)</p> <p>Example value: 300</p> </dd></dl> <p>Supported target-specific variables:</p> <dl> <dt><strong><a name="item_lookup">lookup</a></strong> </dt><dd> <p>Name of the host to look up in the dns.</p> <p>Example value: www.example.org</p> </dd><dt><strong><a name="item_mininterval">mininterval</a></strong> </dt><dd> <p>Minimum time between sending two lookup queries in (possibly fractional) seconds.</p> <p>Default value: 0.5</p> </dd><dt><strong><a name="item_pings">pings</a></strong> </dt><dd> <p>How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them.</p> <p>Example value: 5</p> </dd><dt><strong><a name="item_port">port</a></strong> </dt><dd> <p>The UDP Port to use.</p> <p>Default value: 53</p> </dd><dt><strong><a name="item_recordtype">recordtype</a></strong> </dt><dd> <p>Record type to look up.</p> <p>Default value: A</p> </dd><dt><strong><a name="item_require_answers">require_answers</a></strong> </dt><dd> <p>Only Count Answers with answer count >= this value.</p> <p>Default value: 0</p> </dd><dt><strong><a name="item_require_noerror">require_noerror</a></strong> </dt><dd> <p>Only Count Answers with Response Status NOERROR.</p> <p>Default value: 0</p> </dd><dt><strong><a name="item_timeout">timeout</a></strong> </dt><dd> <p>Timeout for a single request in seconds.</p> <p>Default value: 5</p> </dd></dl> <p> </p> <hr /> <h1><a name="authors">AUTHORS</a></h1> <p>Christoph Heine <<a href="mailto:Christoph.Heine@HaDiKo.DE">Christoph.Heine@HaDiKo.DE</a>></p> </body> </html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
d97b4c58d8763adc61a7b020afdfd868
>
files
>
53
