<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix">
    <title>gmane.comp.monitoring.monitorix</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/152"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/151"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/150"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/149"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/148"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/147"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/146"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/145"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/144"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/143"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/142"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/141"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/140"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/139"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/138"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/137"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/136"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/135"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/134"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/133"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/152">
    <title>Monitorix 3.2.0 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/152</link>
    <description>&lt;pre&gt;Monitorix 3.2.0 has been released!

This version introduces a new major feature. A new graph to monitor the 
sensors of a Raspberry Pi card, which includes its clock frequencies, 
temperature and voltages. This graph requires to have installed the 
command 'vcgencmd' that should come with the Raspberry Pi firmware.

My special thanks to graysky for his suggestion to add this new graph 
and for his assistance during all the process.

Another important new feature is the support of ATI cards in the 
'lmsens' graph which will be able to display its temperature. As in the 
NVIDIA case, it requires the ATI official drivers.

It also includes the new option 'temperature_scale' to be able to toggle 
between values in Celsius or in Fahrenheit in all graphs that show 
temperatures.

The rest of changes and bugs fixed are, as always, reflected in the 
Changes file.

Please, check the monitorix.conf(5) man page for all the details.

IMPORTANT NOTICE: The configuration file monitorix.conf has been 
extended with importa&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-05-13T10:00:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/151">
    <title>Monitorix 3.1.0 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/151</link>
    <description>&lt;pre&gt;Monitorix 3.1.0 has been released!

This is mainly a bug fixing version which also includes a new FTP 
statistics graph. This new graph supports either ProFTPD and vsftpd log 
file formats, and although it covers the most basic aspects of an FTP 
server it should be very useful for daily monitoring.

The main reason of this release though is that a number of important 
bugs were fixed, and so all users still using older Monitorix versions 
are encouraged to upgrade to this one.

Please, read the Changes file to get an idea of the bugs fixed.

NOTICE: The configuration file monitorix.conf has been extended with 
important changes.

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-03-15T08:04:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/150">
    <title>Monitorix 3.0.0 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/150</link>
    <description>&lt;pre&gt;Monitorix 3.0.0 has been released!

Finally the 3.0.0 is out!

With the release of the 3.0.0 version Monitorix suffered another large 
rewrite which became into a complete modular code structure reducing in 
some cases its memory footprint. That new version also includes a number 
of new features, cleaned up all the code, fixed a lot of bugs and has a 
safest code as it uses 'strict' and 'warnings' in all its modules.

With this new modular structure, Monitorix can now be packaged either 
into a single one package (requiring all its dependences to be satisfied 
during the installation), or into several small packages one for each 
graph which should reduce notably its memory footprint.

Another interesting new feature in 3.0.0 version is that Monitorix comes 
with its own HTTP server built in. This should satisfy all the people 
that don't want to install an HTTP server (Apache, Nginx, lighttpd, 
etc.) to see the Monitorix graphs.

Please read the past beta news and the Changes file in order to know all 
the&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-02-18T15:08:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/149">
    <title>Monitorix 3.0.0beta2 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/149</link>
    <description>&lt;pre&gt;Monitorix 3.0.0beta2 has been released!

This new beta release includes a number of improvements in the MySQL 
graph thanks to Luca Ferrario who continuously sends feedback for 
improving such graph.

This new version also includes a new feature in the Network Port traffic 
accounting to support either incoming and outgoing connections. 
Unfortunately this forced to change the internal structure of the 
port.rrd file, so a new one will be rebuilt in the next restart losing 
all the historical data.

Also, there are new alert capabilities in the Mail MTA graph which 
should help to know if the number of delivered messages per minute is 
exceeding some defined threshold and if the mail queue is growing up for 
any reason.

The rest of changes and bugs fixed are, as always, reflected in the 
Changes file.

Please, check the monitorix.conf(5) man page for all the details.

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-02-01T11:28:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/148">
    <title>Monitorix 3.0.0beta1 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/148</link>
    <description>&lt;pre&gt;Monitorix 3.0.0beta1 has been released!

This is the first release of the new 3.0 branch. In this new 3.0.0beta1
version Monitorix has suffered a massive rewrite and now it has a modular
code structure reducing, in some cases, its memory footprint and offering
the ability to package every graph independently, making it more suitable
for embedded systems.

This new version was mainly created to reach the same functionality and
stability level than 2.6.0, therefore it doesn't includes much new
features, although a big number of bugs were fixed. The most important
changes are it's new modular code and that the configuration file is no
longer a Perl file. This should reduce the syntax error problems will make
more friendly the configuration task.

Another important aspect is that this new 3.0 branch don't breaks the
compatibility with the current .rrd files. So you don't need to worry with
your current historical data. The only graph that was affected is pc.rrd
which has been renamed to traffacct.rrd.

Please ta&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-01-12T17:53:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/147">
    <title>Re: Error: Could not lock RRD</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/147</link>
    <description>&lt;pre&gt;Paulo,

Glad to know you managed to solve the problem.
Thank you very much for your kind words on Monitorix.

Best regards.


On 01/09/2013 04:17 PM, Paulo Ribeiro wrote:

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-01-09T15:48:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/146">
    <title>Re: Error: Could not lock RRD</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/146</link>
    <description>&lt;pre&gt;Hello Jordi, thank you for your reply!

I had already deleted the old cron scripts, as I noticed that the new 
version now uses a daemon.

However, your reply gave me an idea:

~$ ps aux | grep 'monitorix'
root     11665  0.0  0.6 115136 12644 ?        Ss   Jan08   1:01 
/usr/bin/monitorix -c /etc/monitorix.conf
root     11767  0.0  0.6 115136 13020 ?        Ss   Jan08   1:01 
/usr/bin/monitorix -c /etc/monitorix.conf
root     12482  0.1  0.9 132588 19560 ?        Ss   11:23   0:25 
/usr/bin/monitorix -c /etc/monitorix.conf -p /var/run/monitorix.pid

For some reason, I had two "rogue" monitorix processes, running without 
the -p switch. I manually killed those and the file lock errors are gone!

Thank you, and congratulations for such a simple and elegant application. :)

&lt;/pre&gt;</description>
    <dc:creator>Paulo Ribeiro</dc:creator>
    <dc:date>2013-01-09T15:17:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/145">
    <title>Re: Error: Could not lock RRD</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/145</link>
    <description>&lt;pre&gt;Hello Paulo,

Those error messages in the log file are of course unexpected.

As you might know your old Monitorix version (probably 1.x branch) used 
the crond to collect data on every minute while the new 2.x branch (as 
you might already know) acts as a daemon.

So, you better check in your /etc/cron.d/ directory to make sure if 
there is a residual 'monitorix' file from the 1.x branch that crond is 
still executing on every minute.

Please, let me know if that solved your problem.
Best regards.



On 01/09/2013 02:37 PM, Paulo Ribeiro wrote:

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2013-01-09T14:16:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/144">
    <title>Error: Could not lock RRD</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/144</link>
    <description>&lt;pre&gt;Hello,

I've been using an older version of Monitorix for a couple of years, but 
yesterday I decided to update to version 2.6.0.

I'm running Ubuntu Server 10.04.4, so I decided to completely remove the 
old version and install the new one using the IzzySoft repository.

Apparently all went well, and Monitorix is up and running. However, in 
the log file I see many errors complaining that Monitorix cannot lock 
some of the .rrd files. For example:

Wed Jan  9 13:23:00 2013 - ERROR: while updating 
/var/lib/monitorix/net.rrd: could not lock RRD
Wed Jan  9 13:23:00 2013 - ERROR: while updating 
/var/lib/monitorix/int.rrd: could not lock RRD
Wed Jan  9 13:24:00 2013 - ERROR: while updating 
/var/lib/monitorix/int.rrd: could not lock RRD
Wed Jan  9 13:27:00 2013 - ERROR: while updating 
/var/lib/monitorix/system.rrd: could not lock RRD
Wed Jan  9 13:27:00 2013 - ERROR: while updating 
/var/lib/monitorix/int.rrd: could not lock RRD
Wed Jan  9 13:28:00 2013 - ERROR: while updating 
/var/lib/monitorix/proc.rrd: co&lt;/pre&gt;</description>
    <dc:creator>Paulo Ribeiro</dc:creator>
    <dc:date>2013-01-09T13:37:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/143">
    <title>Re: mysql.rrd doesn't exist in the /var/lib/monitorix.</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/143</link>
    <description>&lt;pre&gt;Hi,

Once you have enabled the MySQL graph in /etc/monitorix.conf and setup its
related options below in the same file, the next and last step is just
restart Monitorix.

Once restarted, Monitorix will create the 'mysql.rrd' file in the
directory specified in $BASE_LIB option and will start collecting stats
(based in the options previously setup) on every minute. So, you don't
need to download anything.

Please, check the file '/var/log/monitorix' to see if there are some error
messages that might help to know the cause of your problems.

I hope that helped you.
Best regards.



&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-11-09T23:12:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/142">
    <title>mysql.rrd doesn't exist in the/var/lib/monitorix.</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/142</link>
    <description>&lt;pre&gt;Hi, all.

Several days ago, I installed monitorix software on Ubuntu 11.10 Operating
System. I followed the instuctions from the URL

http://www.monitorix.org/doc_debian.html

I decided to active the mysql monitoring option. However, after I updated
the monitorix.conf the system showed the following error:
ERROR: while graphing /usr/share/monitorix/imgs/mysql01.1day.png: opening
'/var/lib/monitorix/mysql.rrd': No such file or directory ERROR

I didn't find the mysql.rrd file in my computer.

Questions:

Do I need to create this file? if so, How?

Or

Do I need to download from Internet? if so, which URL?


Thanks in advance

&lt;/pre&gt;</description>
    <dc:creator>Mónico Briseño</dc:creator>
    <dc:date>2012-11-09T19:17:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/141">
    <title>Re: I just stared experimenting with monitorix, had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/141</link>
    <description>&lt;pre&gt;Dear Jordi Sanfeliu:

Thanks for the pointer. It's exactly what I was looking for.

-Auro


-----Original Message-----
From: Jordi Sanfeliu [mailto:jordi-vR72a6M/EYGr8tq0KR2Zig&amp;lt; at &amp;gt;public.gmane.org] 
Sent: Thursday, November 08, 2012 7:08 AM
To: monitorix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
Subject: Re: [Monitorix-general] I just stared experimenting with monitorix, had some questions

Hello Auro,

On 11/07/2012 05:40 PM, Auro Tripathy wrote:
[...]

Your question seems too generic.

RRDtool has an extensive documentation to learn how to define a RRD database, and understand concepts like GAUGE, COUNTER, etc.

&amp;lt;http://oss.oetiker.ch/rrdtool/doc/index.en.html&amp;gt;

If you need some assistance including support for a new graph into Monitorix, then I recommend you to join to the #monitorix IRC channel at freenode and we can have a more fluid talk about all this.

Regards.

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

-------------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Auro Tripathy</dc:creator>
    <dc:date>2012-11-08T15:46:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/140">
    <title>Re: I just stared experimenting with monitorix, had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/140</link>
    <description>&lt;pre&gt;Hello Auro,

On 11/07/2012 05:40 PM, Auro Tripathy wrote:
[...]

Your question seems too generic.

RRDtool has an extensive documentation to learn how to define a RRD 
database, and understand concepts like GAUGE, COUNTER, etc.

&amp;lt;http://oss.oetiker.ch/rrdtool/doc/index.en.html&amp;gt;

If you need some assistance including support for a new graph into 
Monitorix, then I recommend you to join to the #monitorix IRC channel at 
freenode and we can have a more fluid talk about all this.

Regards.

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-11-08T15:08:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/139">
    <title>Re: I just stared experimenting with monitorix, had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/139</link>
    <description>&lt;pre&gt;Dear Jordi Sanfeliu:

Deeply appreciate your  response. 

I will familiarize myself with RRDtool.  It appears to be a good design choice. Its seems lightweight and better than a SQL-style DB.

Thank you for the tip on changing the duration of the graph. I'm assuming the RRDtools's "circular buffer" also adjusts itself to overwrite after 4 hours as you have shown in the example.

Since our server is hosted on a small 2-6 T byte NAS, we definitely want to monitor some additional services for media serving, transcoding, etc. Please guide us on this step.

-Auro

  
-----Original Message-----
From: Jordi Sanfeliu [mailto:jordi-vR72a6M/EYGr8tq0KR2Zig&amp;lt; at &amp;gt;public.gmane.org] 
Sent: Wednesday, November 07, 2012 3:58 AM
To: monitorix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
Subject: Re: [Monitorix-general] I just stared experimenting with monitorix, had some questions

Hello Auro,

Answering your questions below:

1. Monitorix collects data on every minute (hard coded) and uses RRDtool databases to save s&lt;/pre&gt;</description>
    <dc:creator>Auro Tripathy</dc:creator>
    <dc:date>2012-11-07T16:40:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/138">
    <title>Re: I just stared experimenting with monitorix, had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/138</link>
    <description>&lt;pre&gt;Hello Auro,

Answering your questions below:

1. Monitorix collects data on every minute (hard coded) and uses RRDtool 
databases to save such data. All these .rrd files are preconfigured to 
hold daily, weekly, monthly and yearly average values, and hence are 
files with a fixed size. There isn't any configuration option in 
monitorix.conf that permits you to change the update frequency.

2. As you know in the main page you can only choose between daily, 
weekly, monthly and yearly, but there is trick. Once you pressed the OK 
button you can change the time frame in the URL to ... let's say 4 
hours, just like this:

Original URL:
http://localhost/monitorix-cgi/monitorix.cgi?mode=localhost&amp;amp;graph=_system1&amp;amp;when=1day&amp;amp;color=black

URL with time frame modified:
http://localhost/monitorix-cgi/monitorix.cgi?mode=localhost&amp;amp;graph=_system1&amp;amp;when=4hour&amp;amp;color=black

Let me say you that when you modify time frames you might end up seeing 
'squared' graphs. This is because the time you chose doesn't match with 
any of the&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-11-07T11:58:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/137">
    <title>Re: I just stared experimenting with monitorix, had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/137</link>
    <description>&lt;pre&gt;To change what services are being monitored look through the
monitorix.conf, then just restart monitorix or just reboot

On 7 November 2012 10:43, Auro Tripathy &amp;lt;Auro.Tripathy-Sjgp3cTcYWE&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Spud</dc:creator>
    <dc:date>2012-11-07T00:23:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/136">
    <title>I just stared experimenting with monitorix,had some questions</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/136</link>
    <description>&lt;pre&gt;I tool is great but I'd like to customize it of a performance-characterization/trouble-shooting environment on an networked embedded system.

1.       How can I have more frequent updates? What are the parameters in the .conf file to tweak.

2.       Instead of the chart duration to be 1 day, I need to have the duration to be 4 hours

3.       I want to monitor my own services/perocesses, not the ones listed (ssh, ftp, telnet, samba,..., fail2ban, etc.), How can I do that.
-Auro

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d_______________________________________________
Monitorix-general mailing list
Monitorix-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https&lt;/pre&gt;</description>
    <dc:creator>Auro Tripathy</dc:creator>
    <dc:date>2012-11-06T23:43:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/135">
    <title>Monitorix 2.6.0 released</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/135</link>
    <description>&lt;pre&gt;Monitorix 2.6.0 has been released!

This version introduces several new major features. The first one refers 
to a new graph to monitor an unlimited number of BIND name servers, 
which includes a complete and overall state of a BIND server. Its seven 
nested graphs cover the most important and relevant status information 
which should help System Administrators to monitor it easily. This has 
introduced the new Perl-XML-Simple dependency.

This graph requires a BIND server with version 9.5 or higher, and in 
order to see all statistics provided by BIND you must configure the 
statistics-channels like this:

statistics-channels {
inet 127.0.0.1 port 8053;
};

Another important major feature includes a complete rewriting of the 
Filesystem Usage and I/O Activity graph adding support to monitor 
unlimited filesystems. This graph includes now the disk I/O activity of 
each filesystem defined.

IMPORTANT NOTICE: The configuration of the Filesystem graph has changed 
and this will create a new fs.rrd file losing &lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-09-19T15:46:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/134">
    <title>Re: Question to VirtualHost [working]</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/134</link>
    <description>&lt;pre&gt;Thomas,

Well, I have no plans to support IPMI yet. Mainly because I don't use it 
and so I don't know how it works.

Perhaps in the future, can't tell it now. If you are very interested on 
this we could work together (out of this ML) to include its support. I'm 
currently focused to improve other parts of Monitorix, though.

Regards.



On 06/20/2012 04:20 PM, thomas.trepper-/Z7h2FnBA6MybS5Ee8rs3A&amp;lt; at &amp;gt;public.gmane.org wrote:

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-06-20T16:34:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/133">
    <title>Re: Question to VirtualHost [working]</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/133</link>
    <description>&lt;pre&gt;Thanks a lot guys. By the way: Are there plans to integrate IPMI in future?

Regards,

Thomas







------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>thomas.trepper-/Z7h2FnBA6MybS5Ee8rs3A&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-06-20T14:20:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.monitoring.monitorix/132">
    <title>Re: Question to VirtualHost [working]</title>
    <link>http://permalink.gmane.org/gmane.comp.monitoring.monitorix/132</link>
    <description>&lt;pre&gt;Thomas, glad to know you are enjoying it! :)

Piotr, right, I forgot to say that :)

Best regards.



On 06/20/2012 02:26 PM, thomas.trepper-/Z7h2FnBA6MybS5Ee8rs3A&amp;lt; at &amp;gt;public.gmane.org wrote:

&lt;/pre&gt;</description>
    <dc:creator>Jordi Sanfeliu</dc:creator>
    <dc:date>2012-06-20T13:15:52</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.monitoring.monitorix">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.monitoring.monitorix</link>
  </textinput>
</rdf:RDF>
