Location: PHPKode > projects > NaWui > nawui/cp_main.php
<?

define("PAGE_ID","controlpanel");
define("PAGE_TITLE","Control-Panel");

require_once("includes/main.inc.php");
include_once("html_wrap/head.inc.php");

?>
<br>
<br>
<div align="center">
<table border="1" class="filter" cellspacing="2" cellpadding="2">
<tr>
<td class="filterTitle">Welcome to Nawui's Control-Panel.</td>
</tr>
<tr>
<td class="filterName">
<br>
Here you can control most aspects of Nawui and Nagios configurations:<br>
<br>
<blockquote>
<b>- Importer:</b> Allows to import current Nagios configurations;<br>
<br>
<b>- Exporter:</b> Exports current modifications you have made to your running Nagios process;<br>
<br>
<b>- Verify:</b> Allows for a pre-flight check to inform if there are serious errors that will break your current Nagios process.<br>
<br>
<b>- Nagios.cfg:</b> Here you can customize all aspects of Nagios itself.<br>
<br>
<b>- CGI.cfg:</b> Here you can customize all aspects of Nagios CGI configurations;<br>
<br>
<b>- Nawui Config:</b> Allows to configure Nawui own configurations;<br>
<br>
<b>- Advanced:</b><blockquote>
Allows direct editing of most <u>ONLINE</u> configuration files, both from Nawui and Nagios.<br>
To avoid unspected results, you should first Verify to check for errors, export your configuration data,
and only then you should editing anything by hand.<br>
This should only be used to avoid the need of getting into the command shell, just to check where is 'that error' you are missing
in pre-flight Verify check.<br><br>
<b>Remember</b> that anything you modify by hand will be <u>overwriten</u> in the next export you will made.<br>
</blockquote>
</blockquote>
<br>
<br>
</td>
</tr>
</tr>
</table>
</div>
<?

include_once("html_wrap/tail.inc.php");

?>
Return current item: NaWui