File: README

package info (click to toggle)
cricket 1.0.5-19
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 1,936 kB
  • sloc: perl: 8,276; ansic: 329; sh: 162; makefile: 63; sql: 16
file content (113 lines) | stat: -rw-r--r-- 3,639 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
This directory has contributed goodies and other useful,
but not critical programs in it. Each is documented, sparingly,
below.

leanODBC:

		A Perl extension that wraps some ODBC 3.x Calls.
		For Win32 platform only.

usrModemUsage:

		This tool can be run from Cricket via an EXEC datasource
		to collect stats on the number of modems in use in a
		USR Total Control chassis. Give it hostname and community
		string on the commandline, and it will give you number of
		modems in use and number of modems in negotiation on lines 0
		and 1 of it's output.

pmlines.pl:

		A tool to tell you the total number of modem and ISDN
		sessions active on a Portmaster.

dump-targets:

		Lets you see what collector will be working on before you
		let the collector loose on your config tree. Useful
		for testing out brand new configs.

rrd-dump:

		A simple program to exercise RRD::File, but it could
		also be used to debug problems, etc. If RRD::File is
		lying to you, so will rrd-dump! Be warned!

test-url:

		A script to fetch a URL and tell you how long it took.
		This can be used via an EXEC datasource to monitor
		HTTP and FTP server response times.

listInterfaces:

		Give this script a router name and a community string
		and it will make a set of target definitions for you.
		Very useful!

rrd-tune:

		Use this to force an rrd "tune" operation on parts
		of your config tree. You'll need to use this to make
		changes to rrd-min, rrd-max, or rrd-heartbeat stick
		if you make them after the RRD files already exist.

rrdTuneAberrant.cgi:

		A CGI script meant to be invoked from a web browser that
		invokes the rrdtool tune aberrant-reset option for the specified
		target and ds (datasource):
		rrdTuneAberrant.cgi?target=%2switch-1%2Fport_2&ds=ifOutOctets
		The argument target should be the complete config tree path.
		An inst argument can be used to specify the instance number
		when appropriate.
		Using this script may require the set user-id bit to be enabled:
		chmod 4755 rrdTuneAberrant.cgi

relocate-perl:

		Used during install to fix the location of Perl in the
		#! lines of the scripts.

getFormat.c:

		If you need to port RRD::Format to your architecture,
		you can use this little C program to help out. See
		the comments in ../lib/RRD/Format.pm.

newsstats:
		This script is called by the news-server subtree to
		format stats from INN's ctlinnd command.

generate-statics:

		This is a nifty little tool to take snapshots of the
		GIFs for a bunch of targets and deposit them into
		a directory to be served as parts of static HTML documents.
		This can be used to make Cricket snappier, or to archive
		interesting GIFs in an automated way.

		This script depends on some tags in order to know where
		to put things. Put these tags in your root Defaults file
		in the target dictionary:

		  static-ranges    -> ranges to calculate for (such as d:y) 
		  static-path      -> file system path to place the image 
		  static-name      -> base file name for the image 

		For example:
 
		  static-ranges = d:w:m 
		  static-path   = %auto-base%/../public_html/static/%auto-target-path% 
		  static-name   = %auto-target-name% 

		You either need to edit the script to set $gBaseURL correctly,
		or you need to use -baseURL to set it. (Or, if you are
		feeling lucky, you can ignore it and hope I guessed the right
		URL for your machine. Don't laugh, it might work...)

		Now, put a tag named "generate-static" in any target
		which you want to be generated. Finally, run generate-statics
		from cron. Making HTML pages that incorporate the generated
		image files is left as an exercise to the reader.