File: configcgi.html

package info (click to toggle)
nagios2 2.6-2%2Betch5
  • links: PTS
  • area: main
  • in suites: etch
  • size: 6,856 kB
  • ctags: 4,475
  • sloc: ansic: 64,870; sh: 4,676; makefile: 787; perl: 722
file content (643 lines) | stat: -rw-r--r-- 23,178 bytes parent folder | download | duplicates (2)
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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<head>
<title>CGI Configuration File Options</title>

<STYLE type="text/css">
<!--
        .Default { font-family: verdana,arial,serif; font-size: 8pt; }
        .PageTitle { font-family: verdana,arial,serif; font-size: 12pt; font-weight: bold; }
-->      
</STYLE>

</head>

<body bgcolor="#FFFFFF" text="black" class="Default">

<p>
<div align="center">
<h2 class="PageTitle">CGI Configuration File Options</h2>
</div>
</p>
<hr>

<p>
<strong><u>Notes</u></strong>
</p>
<p>
When creating and/or editing configuration files, keep the following in mind:
</p>
<p>
<ol>
<li>Lines that start with a '#' character are taken to be comments and are not processed
<li>Variables names must begin at the start of the line - no white space is allowed before the name
<li>Variable names are case-sensitive
</ol>
</p>

<p>
<strong><u>Sample Configuration</u></strong>
</p>
<p>
A sample CGI configuration file is created when you run the configure script - you can find the sample config file in the <i>sample-config/</i> subdirectory of the Nagios distribution.
</p>

<p>
<strong><u>Config File Location</u></strong>
</p>
<p>
By default, Nagios expects the CGI configuration file to be named <b>cgi.cfg</b> and located in the config file directory along with the <a href="configmain.html">main config file</a>.  If you need to change the name of the file or its location, you can configure Apache to pass an environment variable named NAGIOS_CGI_CONFIG (which points to the correct location) to the CGIs.  See the Apache documentation for information on how to do this. 
</p>

<p>
<strong><u>Index</u></strong>
</p>
<p>
<a href="#main_cfg_file">Main configuration file location</a><br>
<a href="#physical_html_path">Physical HTML path</a><br>
<a href="#url_html_path">URL HTML path</a><br>
<br>
<a href="#use_authentication">Authentication usage</a><br>
<a href="#default_user_name">Default user name</a><br>
<a href="#authorized_for_system_information">System/process information access</a><br>
<a href="#authorized_for_system_commands">System/process command access</a><br>
<a href="#authorized_for_configuration_information">Configuration information access</a><br>
<a href="#authorized_for_all_hosts">Global host information access</a><br>
<a href="#authorized_for_all_host_commands">Global host command access</a><br>
<a href="#authorized_for_all_services">Global service information access</a><br>
<a href="#authorized_for_all_service_commands">Global service command access</a><br>
<br>
<a href="#statusmap_background_image">Statusmap CGI background image</a><br>
<a href="#default_statusmap_layout">Default statusmap layout method</a><br>
<a href="#statuswrl_include">Statuswrl CGI include world</a><br>
<a href="#default_statuswrl_layout">Default statuswrl layout method</a><br>
<br>
<a href="#refresh_rate">CGI refresh rate</a><br>
<a href="#audio_alerts">Audio alerts</a><br>
<br>
<a href="#ping_syntax">Ping syntax</a><br>
</p>

<p>
<a name="main_cfg_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Main Configuration File Location</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>main_config_file=&lt;file_name&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>main_config_file=/usr/local/nagios/etc/nagios.cfg</strong></font></td>
</tr>
</table>
</p>

<p>
This specifies the location of your <a href="configmain.html">main configuration file</a>.  The CGIs need to know where to find this file in order to get information about configuration information, current host and service status, etc.
</p>

<p>
<a name="physical_html_path"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Physical HTML Path</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>physical_html_path=&lt;path&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>physical_html_path=/usr/local/nagios/share</strong></font></td>
</tr>
</table>
</p>

<p>
This is the <i>physical</i> path where the HTML files for Nagios are kept on your workstation or server.  Nagios
assumes that the documentation and images files (used by the CGIs) are stored in subdirectories called <i>docs/</i> and <i>images/</i>, respectively.
</p>


<p>
<a name="url_html_path"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>URL HTML Path</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>url_html_path=&lt;path&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>url_html_path=/nagios</strong></font></td>
</tr>
</table>
</p>

<p>
If, when accessing Nagios via a web browser, you point to an URL like <b>http://www.myhost.com/nagios</b>, this value
should be <i>/nagios</i>.  Basically, its the path portion of the URL that is used to access the Nagios HTML pages.
</p>


<p>
<a name="use_authentication"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Authentication Usage</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>use_authentication=&lt;0/1&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>use_authentication=1</strong></font></td>
</tr>
</table>
</p>

<p>
This option controls whether or not the CGIs will use the authentication and authorization functionality when determining what information and commands users have access to.  I would strongly suggest that you use the authentication functionality for the CGIs.  If you decide not to use authentication, make sure to remove the <a href="cgis.html#command_cgi">command CGI</a> to prevent unauthorized users from issuing commands to Nagios.  The CGI will not issue commands to Nagios if authentication is disabled, but I would suggest removing it altogether just to be on the safe side.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't use authentication functionality
<li>1 = Use authentication and authorization functionality (default)
</ul>
</p>


<p>
<a name="default_user_name"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Default User Name</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>default_user_name=&lt;username&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>default_user_name=guest</strong></font></td>
</tr>
</table>
</p>

<p>
Setting this variable will define a default username that can access the CGIs.  This allows people within a secure domain (i.e., behind a firewall) to access the CGIs without necessarily having to authenticate to the web server.   You may want to use this to avoid having to use basic authentication if you are not using a secure server, as basic authentication transmits passwords in clear text over the Internet.
</p>
<p>
<strong>Important:</strong>  Do <i>not</i> define a default username unless you are running a secure web server and are sure that everyone who has access to the CGIs has been authenticated in some manner!  If you define this variable, anyone who has not authenticated to the web server will inherit all rights you assign to this user!
</p>

<p>
<a name="authorized_for_system_information"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>System/Process Information Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_system_information=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_system_information=nagiosadmin,theboss</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can view system/process information in the <a href="cgis.html#extinfo_cgi">extended information CGI</a>.  Users in this list are <i>not</i> automatically authorized to issue system/process commands.  If you want users to be able to issue system/process commands as well, you must add them to the <a href="#authorized_for_system_commands">authorized_for_system_commands</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_system_commands"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>System/Process Command Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_system_commands=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_system_commands=nagiosadmin</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can issue system/process commands via the <a href="cgis.html#cmd_cgi">command CGI</a>.  Users in this list are <i>not</i> automatically authorized to view system/process information.  If you want users to be able to view system/process information as well, you must add them to the <a href="#authorized_for_system_information">authorized_for_system_information</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_configuration_information"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Configuration Information Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_configuration_information=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_configuration_information=nagiosadmin</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can view configuration information in the <a href="cgis.html#config_cgi">configuration CGI</a>.  Users in this list can view information on all configured hosts, host groups, services, contacts, contact groups, time periods, and commands.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_all_hosts"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Host Information Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_all_hosts=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_all_hosts=nagiosadmin,theboss</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can view status and configuration information for all hosts.  Users in this list are also automatically authorized to view information for all services.  Users in this list are <i>not</i> automatically authorized to issue commands for all hosts or services.  If you want users able to issue commands for all hosts and services as well, you must add them to the <a href="#authorized_for_all_host_commands">authorized_for_all_host_commands</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_all_host_commands"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Host Command Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_all_host_commands=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_all_host_commands=nagiosadmin</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can issue commands for all hosts via the <a href="cgis.html#cmd_cgi">command CGI</a>.  Users in this list are also automatically authorized to issue commands for all services.  Users in this list are <i>not</i> automatically authorized to view status or configuration information for all hosts or services.  If you want users able to view status and configuration information for all hosts and services as well, you must add them to the <a href="#authorized_for_all_hosts">authorized_for_all_hosts</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_all_services"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Service Information Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_all_services=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_all_services=nagiosadmin,theboss</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can view status and configuration information for all services.  Users in this list are <i>not</i> automatically authorized to view information for all hosts.  Users in this list are <i>not</i> automatically authorized to issue commands for all services.  If you want users able to issue commands for all services as well, you must add them to the <a href="#authorized_for_all_service_commands">authorized_for_all_service_commands</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="authorized_for_all_service_commands"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Service Command Access</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>authorized_for_all_service_commands=&lt;user1&gt;,&lt;user2&gt;,&lt;user3&gt;,...&lt;user<i>n</i>&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>authorized_for_all_service_commands=nagiosadmin</strong></font></td>
</tr>
</table>
</p>

<p>
This is a comma-delimited list of names of <i>authenticated users</i> who can issue commands for all services via the <a href="cgis.html#cmd_cgi">command CGI</a>.  Users in this list are <i>not</i> automatically authorized to issue commands for all hosts.  Users in this list are <i>not</i> automatically authorized to view status or configuration information for all hosts.  If you want users able to view status and configuration information for all services as well, you must add them to the <a href="#authorized_for_all_services">authorized_for_all_services</a> variable.  More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>.
</p>


<p>
<a name="statusmap_background_image"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Statusmap CGI Background Image</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>statusmap_background_image=&lt;image_file&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>statusmap_background_image=smbackground.gd2</strong></font></td>
</tr>
</table>
</p>

<p>
This option allows you to specify an image to be used as a background in the <a href="cgis.html#statusmap_cgi">statusmap CGI</a> if you use the user-supplied coordinates layout method.  The background image is not be available in any other layout methods.  It is assumed that the image resides in the HTML images path (i.e. /usr/local/nagios/share/images). This path is automatically determined by appending "/images" to the path specified by the <a href="#physical_html_path">physical_html_path</a> directive.  Note: The image file can be in GIF, JPEG, PNG, or GD2 format.  However, GD2 format (preferably in uncompressed format) is recommended, as it will reduce the CPU load when the CGI generates the map image.
</p>


<p>
<a name="default_statusmap_layout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Default Statusmap Layout Method</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>default_statusmap_layout=&lt;layout_number&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>default_statusmap_layout=4</strong></font></td>
</tr>
</table>
</p>

<p>
This option allows you to specify the default layout method used by the <a href="cgis.html#statusmap_cgi">statusmap CGI</a>. Valid options are:
</p>

<p>
<table border=1 cellspacing=0 cellpadding=5 class="Default">
<tr><th>&lt;layout_number&gt; Value</th><th>Layout Method</th></tr>
<tr><td>0</td><td>User-defined coordinates</td></tr>
<tr><td>1</td><td>Depth layers</td></tr>
<tr><td>2</td><td>Collapsed tree</td></tr>
<tr><td>3</td><td>Balanced tree</td></tr>
<tr><td>4</td><td>Circular</td></tr>
<tr><td>5</td><td>Circular (Marked Up)</td></tr>
<tr><td>6</td><td>Circular (Balloon)</td></tr>
</table>
</p>


<p>
<a name="statuswrl_include"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Statuswrl CGI Include World</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>statuswrl_include=&lt;vrml_file&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>statuswrl_include=myworld.wrl</strong></font></td>
</tr>
</table>
</p>

<p>
This option allows you to include your own objects in the generated VRML world.  It is assumed that the file resides in the path specified by the <a href="#physical_html_path">physical_html_path</a> directive.  Note:  This file must be a fully qualified VRML world (i.e. you can view it by itself in a VRML browser).
</p>



<p>
<a name="default_statuswrl_layout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Default Statuswrl Layout Method</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>default_statuswrl_layout=&lt;layout_number&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>default_statuswrl_layout=4</strong></font></td>
</tr>
</table>
</p>

<p>
This option allows you to specify the default layout method used by the <a href="cgis.html#statuswrl_cgi">statuswrl CGI</a>. Valid options are:
</p>

<p>
<table border=1 cellspacing=0 cellpadding=5 class="Default">
<tr><th>&lt;layout_number&gt; Value</th><th>Layout Method</th></tr>
<tr><td>0</td><td>User-defined coordinates</td></tr>
<tr><td>2</td><td>Collapsed tree</td></tr>
<tr><td>3</td><td>Balanced tree</td></tr>
<tr><td>4</td><td>Circular</td></tr>
</table>
</p>


<p>
<a name="refresh_rate"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>CGI Refresh Rate</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>refresh_rate=&lt;rate_in_seconds&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>refresh_rate=90</strong></font></td>
</tr>
</table>
</p>

<p>
This option allows you to specify the number of seconds between page refreshes for the <a href="cgis.html#status_cgi">status</a>, <a href="cgis.html#statusmap_cgi">statusmap</a>, and <a href="cgis.html#extinfo_cgi">extinfo</a> CGIs.
</p>


<p>
<a name="audio_alerts"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Audio Alerts</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Formats:</td>
<td>
<strong>host_unreachable_sound=&lt;sound_file&gt;</strong><br>
<strong>host_down_sound=&lt;sound_file&gt;</strong><br>
<strong>service_critical_sound=&lt;sound_file&gt;</strong><br>
<strong>service_warning_sound=&lt;sound_file&gt;</strong><br>
<strong>service_unknown_sound=&lt;sound_file&gt;</strong><br>
</td>
</tr>
<tr>
<td valign=top>Examples:</td>
<td>
<font color="red"><strong>host_unreachable_sound=hostu.wav</strong></font><br>
<font color="red"><strong>host_down_sound=hostd.wav</strong></font><br>
<font color="red"><strong>service_critical_sound=critical.wav</strong></font><br>
<font color="red"><strong>service_warning_sound=warning.wav</strong></font><br>
<font color="red"><strong>service_unknown_sound=unknown.wav</strong></font><br>
</td>
</tr>
</table>
</p>

<p>
These options allow you to specify an audio file that should be played in your browser if there are problems when you are viewing the <a href="cgis.html#status_cgi">status CGI</a>.  If there are problems, the audio file for the most critical type of problem will be played.  The most critical type of problem is on or more unreachable hosts, while the least critical is one or more services in an unknown state (see the order in the example above).  Audio files are assumed to be in the <b>media/</b> subdirectory in your HTML directory (i.e. <i>/usr/local/nagios/share/media</i>).
</p>

<p>
<a name="ping_syntax"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Ping Syntax</strong></td>
</tr>
</table>
</p>

<p>
<table border="0" class="Default">
<tr>
<td valign=top>Format:</td>
<td><strong>ping_syntax=&lt;command&gt;</strong></td>
</tr>
<tr>
<td valign=top>Example:</td>
<td><font color="red"><strong>ping_syntax=/bin/ping -n -U -c 5 $HOSTADDRESS$</strong></font></td>
</tr>
</table>
</p>

<p>
This option determines what syntax should be used when attempting to ping a host from the WAP interface (using
the <a href="cgis.html#statuswml_cgi">statuswml CGI</a>.  You must include the full path to the ping binary, along with all required options.  The $HOSTADDRESS$ macro is substituted with the address of the host before the command is executed.
</p>


<hr>

</body>
</html>