Smokeping_probes_EchoPingIcp man page on Alpinelinux

Man page or keyword search:  
man Server   18016 pages
apropos Keyword Search (all sections)
Output format
Alpinelinux logo
[printable version]

Smokeping_probes_EchoPingIcp(3)	   SmokePing   Smokeping_probes_EchoPingIcp(3)

NAME
       Smokeping::probes::EchoPingIcp - an echoping(1) probe for SmokePing

OVERVIEW
       Measures ICP (Internet Cache Protocol, spoken by web caches) roundtrip
       times for SmokePing.

SYNOPSIS
	*** Probes ***

	+EchoPingIcp

	binary = /usr/bin/echoping
	forks = 5
	offset = 50%
	step = 300

	# The following variables can be overridden in each target section
	extraopts = -some-letter-the-author-did-not-think-of
	ipversion = 4
	pings = 5
	priority = 6
	timeout = 1
	tos = 0xa0
	url = http://www.example.org/ # mandatory
	waittime = 1

	# [...]

	*** Targets ***

	probe = EchoPingIcp # if this should be the default probe

	# [...]

	+ mytarget
	# probe = EchoPingIcp # if the default probe is something else
	host = my.host
	extraopts = -some-letter-the-author-did-not-think-of
	ipversion = 4
	pings = 5
	priority = 6
	timeout = 1
	tos = 0xa0
	url = http://www.example.org/ # mandatory
	waittime = 1

VARIABLES
       Supported probe-specific variables:

       binary
	   The location of your echoping binary.

	   Default value: /usr/bin/echoping

       forks
	   Run this many concurrent processes at maximum

	   Example value: 5

	   Default value: 5

       offset
	   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.)

	   Example value: 50%

       step
	   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.)

	   Example value: 300

       Supported target-specific variables:

       extraopts
	   Any extra options specified here will be passed unmodified to
	   echoping(1).

	   Example value: -some-letter-the-author-did-not-think-of

       ipversion
	   The IP protocol used. Possible values are "4" and "6".  Passed to
	   echoping(1) as the "-4" or "-6" options.

	   Example value: 4

       pings
	   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.

	   Example value: 5

       priority
	   The "-p" echoping(1) option.

	   Example value: 6

       timeout
	   The "-t" echoping(1) option.

	   Example value: 1

	   Default value: 5

       tos The "-P" echoping(1) option.

	   Example value: 0xa0

       url The URL to be requested from the web cache.

	   Example value: http://www.example.org/

	   This setting is mandatory.

       waittime
	   The "-w" echoping(1) option.

	   Example value: 1

AUTHORS
       Niko Tyni <ntyni@iki.fi>

NOTES
       The fill, size and udp EchoPing variables are not valid.

SEE ALSO
       Smokeping::probes::EchoPing, Smokeping::probes::EchoPingHttp

2.6.9				  2014-05-15   Smokeping_probes_EchoPingIcp(3)
[top]

List of man pages available for Alpinelinux

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net