Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > d97b4c58d8763adc61a7b020afdfd868 > files > 65

smokeping-2.4.2-9mdv2010.0.noarch.rpm

<?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/DNS</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::DNS - Name Service Probe for SmokePing</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
 *** Probes ***</pre>
<pre>
 +DNS</pre>
<pre>
 binary = /usr/bin/dig # mandatory
 forks = 5
 offset = 50%
 step = 300
 timeout = 15</pre>
<pre>
 # The following variables can be overridden in each target section
 lookup = www.example.org
 pings = 5
 server = ns1.someisp.net</pre>
<pre>
 # [...]</pre>
<pre>
 *** Targets ***</pre>
<pre>
 probe = DNS # if this should be the default probe</pre>
<pre>
 # [...]</pre>
<pre>
 + mytarget
 # probe = DNS # if the default probe is something else
 host = my.host
 lookup = www.example.org
 pings = 5
 server = ns1.someisp.net</pre>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>Integrates dig as a probe into smokeping. The variable <strong>binary</strong> must
point to your copy of the dig program. If it is not installed on
your system yet, you should install bind-utils &gt;= 9.0.0.</p>
<p>The Probe asks the given host n-times for it's name. Where n is
the amount specified in the config File.</p>
<p>
</p>
<hr />
<h1><a name="variables">VARIABLES</a></h1>
<p>Supported probe-specific variables:</p>
<dl>
<dt><strong><a name="item_binary">binary</a></strong>

</dt><dd>
<p>The location of your dig binary.</p>
<p>Example value: /usr/bin/dig</p>
<p>This setting is mandatory.</p>

</dd><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><dt><strong><a name="item_timeout">timeout</a></strong>

</dt><dd>
<p>How long a single 'ping' takes at maximum</p>
<p>Example value: 15</p>
<p>Default value: 5</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_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_server">server</a></strong>

</dt><dd>
<p>Name of the dns server to use.</p>
<p>Example value: ns1.someisp.net</p>

</dd></dl>
<p>
</p>
<hr />
<h1><a name="authors">AUTHORS</a></h1>
<pre>
 Igor Petrovski &lt;pigor@myrealbox.com&gt;,
 Carl Elkins &lt;carl@celkins.org.uk&gt;,
 Andre Stolze &lt;stolze@uni-muenster.de&gt;,
 Niko Tyni &lt;ntyni@iki.fi&gt;,
 Chris Poetzel&lt;cpoetzel@anl.gov&gt;</pre>

</body>

</html>