NOTE
----
The configuration file is a perl file where you set the value directly to the
variables that Monitorix will use during its normal operation. So you must take
special attention to not break some basic syntax. I mean, every variable need
to terminate with a semicolon ";".

Following there is a description of all the configuration variables:

TITLE
Set your company name. Not relevant.
Default is "FIBRANET NSP, SL".


HOSTNAME
Sometimes you want to hide the real name of your host. With this variable
you can do that.
Default is null.


OSTYPE
This option helps to be more operating system portable, in order to take care
about different paths with the log files and some binaries. At this time
Monitorix supports the following operating systems:
	- Linux-RHFC	(RedHat/Fedora/CentOS)
	- Linux-Debian	(Debian)
	- Linux-Gentoo	(Gentoo)
	- FreeBSD	(FreeBSD systems)
You are encouraged to add new ones like "Linux-SUSE", "Linux-Mandrake", etc.


IDATE
It is just a recordatory, but useful to know when it beguns. Not relevant.
Default is "01 Jan 2007".


SAMBAVER
Set your current Samba version: 2 or 3. Don't worry if you don't have Samba.
Default is "3".


MULTIHOST
If you only have one server (or laptop) just leave with "N", otherwise set "Y".
In that case, you'll have to install Monitorix in the other servers. You don't
need to setup this variable in the other servers. This is not relevant.
Next you will want to setup the list of servers where the Monitorix is running
on. See SERV_LIST to know how do that.
Default is "N".


MULTIHOST_FOOTER
If set to "Y" Monitorix will show the URL of the server below the graph.
Only where the security it's very important you may want to be silent about
this aspect.
Default is "Y".


MULTIHOST_IMGPERLINE
If your screen resolution is large (1280x1024 or more), your browser may fit
more than 2 or 3 graphs per line. This variable sets this.
Default is "2".


REPORT_LANG
The language of the report, only "ca" or "en" at this moment.
The first day of each month, if configured, Monitorix will send to the
specified email address, a report of all the monthly Internet activity of the
pre-selected PCs in the LAN.
Default is "en",


THEME_COLOR
At this moment only exist two predefined themes. Black or white.
Default is "black".


EMAIL
Default email address to send the monthly reports.
Default is "root@localhost".


REFRESH_RATE
The refresh rate of the statistics web page (in seconds).
Default is 150.


ENABLE_CPU, ENABLE_KERN, ENABLE_PROC, ENABLE_DISK, etc.
These variables determine if each graph is enabled of disabled at all. These
are specially important in embedded systems where the disk space and the
processor performance is lower.
By default all the graphs are enabled (with "Y" or any other than "N") except
the LM-Sensors graphs (ENABLE_LMTEMP). If your system has enabled the lm_sensors
and has the hddtemp tool you can start getting the temperatures of your core
devices.


ENABLE_ZOOM
When enabled it permits to click on any graph image and see a bigger picture of
it. Useful when you need to see the picture in more detail.
Default is enabled.


CPU1_* and CPU2_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all relaxed.


MEMORY
Put here the amount of physical memory of your system.


MACHINE
If your system is a Hewlett-Packard ProLiant server and is one of these
supported systems, you'll want specify this in order to get temperatures
results.
HP Insight Management Agent must be installed on that server.


SENSORS_LIST
When temperatures are enabled you can specify in this associative array the
devices you want monitorize with the names that appear with your 'sensors'
command.
For example, imagine the output of your 'sensors' command is:

Temp1/CPU:      +36.00 C
Temp2/MB:       +29.00 C
Temp3/AUX:      failed
Fan1:             1440 RPM
Fan2:                0 RPM
Fan3:             3420 RPM
+12V:           +11.75 V
+5V:             +5.12 V
Battery:         +3.03 V

Then your SENSORS_LIST array will be:
our %SENSORS_LIST = ("MB" => "Temp2/MB",
                     "CPU1" => "Temp1/CPU",
		     "FAN1" => "Fan1",
		     "FAN2" => "Fan2",
		     "FAN3" => "Fan3");

Possible key values are: MB, CPU1, CPU2, CPU3, CPU4, FAN1, FAN2 and FAN3.


HDDTEMP_LIST
The list of hard drives you want monitorize with 'hddtemp' tool. The maximum
allowed is 9.


MNT_LIST
List of mounted filesystem, not including the root filesystem (/). The
maximum allowed is 7.


MNT_ACOL and MNT_LCOL
List of filesystem area and line colors.


DISK2_* and DISK3_
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all relaxed.


NET_LIST
List of the network devices defined in the system. The maximum allowed is 5.


NET_TYPE
List of the network device description.


NET_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is not rigid.


INETIF
The network device that acts as a gateway on your system.
Default is eth0.


SERVU1_*, SERVU2_* and SERVU3_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all relaxed.


PORT01 thru PORT12
Specify here the port numbers you want to be scanned by Monitorix to show
activity. For those ports you don't want monitorize, please leave the variable
defined as simply "our $PORTnn;" (without quotes) where nn is the port number.
By default there are some of the most importants.


PORT01_NAME thru PORT12_NAME
Specify here the names of those ports selected above.
activity. For those ports you don't want monitorize, please leave the variable
defined as simply "our $PORTnn_NAME;" (without quotes) where nn is the port
number.
By default there are some of the most importants.


PORT01_* thru PORT12_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all fixed.


USER1_* thru USER3_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all relaxed.


INT1_* thru INT3_*
See the first lines of the configuration file to know how to setup the
RIGID and LIMIT variables.
Default is all relaxed.


SERV_LIST
List of other servers running Monitorix you want to monitorize.
An example of that is:
our @SERV_LIST=("server number one", "http://192.168.1.10",
		"server number two", "http://192.168.1.11");
... and so on. (Take care with the Perl syntax).


BLACK
List of predefined colors for the black theme. The white theme is the default
color in the rrdtool.


PC_DEFMAIL
Destination email address for the monthly reports.


PC_MAIL
List of destination email address for each defined PC on LAN.


PC_MAX
Maximum of PC monitorized. If you need to increment this value you'll have
to modify too the shell-script /usr/sbin/monitorix.pl, in the create section,
in the rrd_pc function.
Default is 100.


PC_LIST and PC_IP
These two lists corresponts to the PC that are desired to be monitorized on LAN.
The PC_IP list is only needed if you want to monitorize an entire network. So
in that case you'll have to insert the mask like this:

our @PC_LIST = ("department1",		# list of pc on LAN (DNS name)
		"department2",
		"office1",
		"office2");
our @PC_IP   = ("192.168.0.176/28",	# list of pc on LAN (IP address + mask)
		"192.168.0.16/28",
		"192.168.0.160/28",
		"192.168.0.80/28");



PORTABILITY TO OTHER SYSTEMS
----------------------------
In the Path variables section you can add new portabilities to other *NIX
systems and/or Linux distributions.

Every line in each array contains a pair of values: the operating system and the
path. Please respect the terminology that every Linux distribution must have
prefixed with the word "Linux-" and then add the primary name of your
distribution using uppercase.

Some examples of different *NIX systems and/or Linux distributions would be:
	- Linux-SUSE
	- Linux-Ubuntu
	- OpenBSD
	- NetBSD
... and so on.