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
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
.\"Created by graziano obertelli <graziano@cs.ucsb.edu>
.\"
.TH start_activity 1 "September 27, 2002" "start_activity"
.SH NAME
start_activity \- instructs the Network Weather Service to start monitoring resources
.SH SYNOPSIS
.B start_activity
[-F][-a][-f file] host [attribute:value ...]
.SH DESCRIPTION
This manual page explains the
.B start_activity
program. You can start to monitor resources using
.B start_activity
and you can use
.B halt_activity(1)
to stop the monitoring.
.B start_activity
contacts a
.B nws_sensor(1)
running on
.I host
and instructs it to start the activity specified by
.I attribute:value.
Here is a list of attribute you can specify (is not complete)
.B name
.RS
specifies the unique name that specifies the activity to be started. If
you don't specify one, an automatic one will be generated.
.RE
.B skillName
.RS
specify the resource that can be monitored (cpuMonitor, diskMonitor, memoryMonitor, tcpConnectMonitor, tcpMessageMonitor)
.RE
.B controlName
.RS
specify the control that is ultimately responsible for how frequently
measurements are taken.
.B periodic
and
.B clique
are the allowed values: the former takes one host measurements
(cpuMonitor) and the latter takes care of the multiple host measurements
(tcpMessageMonitor)
.RE
.B member
.RS
specify a host that is part of this clique. Tipically you will have at
least 2 of these options. You can specify members with the
.I host:port
format. Currently there is a limitation of 100 member for a clique.
.RE
.B period
.RS
specify how many seconds between measurements.
.RE
.B size
.RS
specify the size of the experiment to be conducted (valid only for
2 hosts experiments like bandwidth experiment). This is the
.B total
number of kB sent for a single experiment (default is 64 for versions 2.6
and smaller, 256 for the others).
.RE
.B message
.RS
specify the size of the messagei (measured in kB) to be used during
network experiments. It cannot be bigger then what specify by
.I size.
Default is 16 kB.
.RE
.B buffer
.RS
specify the buffer to be requested when opening a socket to conduct a
network experiment (measured in kB). Not all systems allows the user to
change this value: NWS will revert to what is allowed in this case.
Default is 32 kB.
.RE
You can see
.B EXAMPLES
later on for a simple example.
.B
.SH OPTIONS
.BI -F
.RS
force the
.B nws_sensor
to start the activity even if a record still exists in the
.B nws_nameserver
.RE
.B -a
.RS
restart all activities on this host
.RE
.BI -f\ file
.RS
read attribute:value from
.I file
instead of the command line.
.RE
.SH EXAMPLES
Let's suppose we have few machines already running
.B nws_sensor(1)
and that we want these nodes to begin performing measurements (of latency and bandwidth in this example). Let A, B and C be three such hosts. You can create a configuration file that defines this situation and then execute start_activity to refer to this configuration using the -f switch. Here is a sample configuration file:
.RS
name:pippo
.RE
.RS
controlName:clique
.RE
.RS
skillName:tcpMessageMonitor
.RE
.RS
member:A
.RE
.RS
member:B
.RE
.RS
member:C
.RE
.RS
size:32
.RE
.RS
period:120
.RE
This instucts the sensors to form a clique named
.I pippo
whose members are A, B and C, that uses a message size of 32K and that
takes measurements every 120 seconds. The command line will be
.P
.B start_activity
-f
.I file
A
.SH BUGS
.P
Bugs list is at
.UR http://nws.cs.ucsb.edu
http://nws.cs.ucsb.edu.
.UE
.SH AUTHOR
NWS is an original idea of Rich Wolski Rich Wolski (rich@cs.ucsb.edu) who
came up with the original
.B nws_memory.
.P
Neil Spring, Jim Hayes (jhayes@cs.ucsd.edu) and Martin Swany maintained
and enhanced it.
.P
Graziano Obertelli (graziano@cs.ucsb.edu) currently maintains NWS and
wrote this man page.
.SH SEE ALSO
.BR nws_sensor(1),
.BR nws_search(1),
.BR nws_nameserver(1),
.BR nws_extract(1)
.BR halt_activity(1)
|
