X-Git-Url: http://git.wpitchoune.net/gitweb/?a=blobdiff_plain;f=doc%2Ffaq.html;h=1fa996b6e0fbe6fccc1ef8b5b142cf2f25a06741;hb=0f96508bf672cf1b4dba1834af9ddd9d39ba7eb5;hp=7b2a32d60019bb58bac00c950e8bce191241600d;hpb=6c6fe4b1da3ed22d8c86b5ed0aaf06a984c710d0;p=psensor.git

diff --git a/doc/faq.html b/doc/faq.html
index 7b2a32d..1fa996b 100644
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -3,142 +3,182 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.6" />
+<meta name="generator" content="AsciiDoc 8.6.9" />
 <title>Psensor Frequently Asked Questions</title>
 <style type="text/css">
+
 body {
-    padding: 1em 1em 1em 1em;
-    font-family: "Ubuntu", sans-serif;
-    font-size: 100%;
-    font-style: normal;
-    font-weight: normal;
-    color: #000;
-    background-color: #fff;
-    margin: 0 0 0 0;
+    background: #e2e2e2;
+    color: #333333;
+    font-family: Ubuntu,Arial,sans-serif;
+    line-height: 1.6;
+    font-weight: lighter;
+    margin: 1em 2em 2em 2em;
+    padding: 0 0 0 0;
 }
 
-a {
-    color: #1982D1;
-    font-style: normal;
-    text-decoration: none;
+h1 {
+    font-size: 2.813em;
+    margin: 0 0 0.267em 0;
+    padding: 0 0 0 0;
+    font-weight: normal;
 }
 
-a:hover {
-    text-decoration: underline;
+h2 {
+    font-size: 2em;
+    margin: 0 0 0.375em;
+    padding: 0 0 0 0;
+    font-weight: normal;
 }
 
-h1 {
-    font-size: 140%;
-    font-style: normal;
-    font-weight: bold;
-    text-transform: uppercase;
-    margin: 0 0 1em 0;
+h3 {
+    font-size: 1.438em;
+    margin: 0 0 0.522em;
     padding: 0 0 0 0;
+    font-weight: normal;
 }
 
+h4 {
+    font-size: 1.219em;
+    margin: 0 0 0.615em;
+    padding: 0 0 0 0;
+    font-weight: normal;
+}
 
-h2, #toctitle{
-    font-size: 110%;
-    font-style: normal;
+h5 {
+    font-size: 1em;
+    margin: 0 0 0.75em;
+    padding: 0 0 0 0;
     font-weight: bold;
+}
+
+h6 {
+    font-weight: normal;
+    font-size: 0.813em;
+    letter-spacing: 0.1em;
+    margin: 0 0 0.923em;
     text-transform: uppercase;
-    margin: 2em 0em 1em 0em;
     padding: 0 0 0 0;
 }
 
-#footer {
-    padding-top: 2em;
-    color: #666;
-    clear: both;
-    text-align: right;
-    font-size: 75%;
+li {
+    margin: 0 0 0 1em;
+    line-height: 1.6;
 }
 
-p {
-    font-size: 100%;
-    margin-bottom: 8px;
+li p {
+    margin: 0 0 0 0;
 }
 
-table {
-    text-align: left;
+ul {
+    margin: 0 0 0 0;
     padding: 0 0 0 0;
-    min-width: 50%;
-    border-spacing: 0;
-    border: 0;
 }
 
-thead {
-    background-color: #000;
-    color: #fff;
-    padding: 0 0 0 0;
+a:link, a:visited {
+    color: #19B6EE;
+    text-decoration: none;
 }
 
-tbody {
-    padding: 0 0 0 0;
+a:hover {
+    text-decoration: underline;
 }
 
-th {
-    padding: 0.25em 0.5em 0.25em 0.5em;
-    font-style: normal;
+code, pre, tt {
+    font-family: "Ubuntu Mono","Courier New",Courier,monospace;
     font-weight: normal;
+    color: #333333;
 }
 
-td {
-    padding: 0.25em 0.25em 0em 0.25em;
+pre {
+    background: none repeat scroll 0 0 #e0e0e0;
+    border-radius: 4px;
+    padding: 0.5em 0.5em;
+    margin: 0 0 0 0;
+    white-space: pre-wrap;
+    word-wrap: break-word;
 }
 
-#chart {
-    color: #000;
-    font-style: normal;
-    font-weight: normal;
+table {
     width: 100%;
-    height: 300px;
+    text-align: left;
 }
 
-ul#menu-list li {
-    list-style: none;
+#footer {
+    margin: 0 0 0 0;
+    font-size: 0.8em;
+    font-weight: lighter;
+    clear: both;
+    text-align: right;
 }
 
-#menu-list {
-    padding: 0 0 0 0;
+#page {
     margin: 0 0 0 0;
+    padding: 0 0 0 0;
+}
+
+#main {
+    background: #ffffff;
+
+   -moz-box-sizing: border-box;
+
+    padding: 2em 2em 2em 2em;
+
+    -moz-border-radius: 4px;
+    -webkit-border-radius: 4px;
+    border-radius: 4px;
+
+    -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
+    box-shadow: 0 2px 2px 0 #C2C2C2;
+}
+
+#menu {
+    background: #ffffff;
+   -moz-box-sizing: border-box;
+    padding: 2em 2em 2em 2em;
+
+    -moz-border-radius: 4px;
+    -webkit-border-radius: 4px;
+    border-radius: 4px;
+
+    -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
+    box-shadow: 0 2px 2px 0 #C2C2C2;
+}
+
+#menu-list, #menu-list > li > ul  {
+    list-style-type: none;
 }
 
+/* menu on left col, content on right col */
+
 #menu {
     float: left;
-    width: 20%;
-    padding: 0 0 0 0;
-    margin: 0 0 0 0;
+    width: 18%;
 }
 
 #main {
     float: right;
     width: 80%;
-    padding: 0 0 0 0;
-    margin: 0 0em 0 0;
 }
 
-em {
-    font-weight: bold;
-    font-style: normal;
-}
+/* asciidoc */
 
-#uptime {
-    font-weight: normal;
-}
+#toc, #content {
+    margin: 0em 0em 2em 0em;
 
-#menu-list em {
-    text-transform: uppercase;
-}
+    background: #ffffff;
+   -moz-box-sizing: border-box;
+    padding: 2em 2em 2em 2em;
 
-#menu ul li {
-    padding-bottom: 1em;
-}
+    -moz-border-radius: 4px;
+    -webkit-border-radius: 4px;
+    border-radius: 4px;
 
-#menu-list ul li {
-    padding: 0 0 0 0em;
+    -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
+    box-shadow: 0 2px 2px 0 #C2C2C2;
 }
 
+
 </style>
 <script type="text/javascript">
 /*<![CDATA[*/
@@ -183,7 +223,7 @@ toc: function (toclevels) {
 
   function tocEntries(el, toclevels) {
     var result = new Array;
-    var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');
+    var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
     // Function that scans the DOM tree for header elements (the DOM2
     // nodeIterator API would be a better technique but not supported by all
     // browsers).
@@ -212,7 +252,7 @@ toc: function (toclevels) {
   var i;
   for (i = 0; i < toc.childNodes.length; i++) {
     var entry = toc.childNodes[i];
-    if (entry.nodeName == 'div'
+    if (entry.nodeName.toLowerCase() == 'div'
      && entry.getAttribute("class")
      && entry.getAttribute("class").match(/^toclevel/))
       tocEntriesToRemove.push(entry);
@@ -258,7 +298,7 @@ footnotes: function () {
   var entriesToRemove = [];
   for (i = 0; i < noteholder.childNodes.length; i++) {
     var entry = noteholder.childNodes[i];
-    if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
+    if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
       entriesToRemove.push(entry);
   }
   for (i = 0; i < entriesToRemove.length; i++) {
@@ -344,17 +384,23 @@ asciidoc.install(2);
 </div>
 </div>
 <div id="content">
+<div id="preamble">
+<div class="sectionbody">
+<div class="paragraph"><p>The last version of this FAQ is available at <a href="http://wpitchoune.net/gitweb/?p=psensor.git;a=blob_plain;f=doc/faq.html;hb=HEAD">http://wpitchoune.net/gitweb/?p=psensor.git;a=blob_plain;f=doc/faq.html;hb=HEAD</a>.</p></div>
+</div>
+</div>
 <div class="sect1">
 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
+<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the
+information about the computer:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
 motherboard and CPUs sensors: the information is retrieved
           from the lm-sensors library, it requires that
-          âsensors-detectâ has been run and the kernel module
-          correctly installed. âsensorsâ can be used for checking.
+          <code>sensors-detect</code> has been run and the kernel module
+          correctly installed. <code>sensors</code> can be used for checking.
 </p>
 </li>
 <li>
@@ -372,13 +418,13 @@ Opensource drivers (nouveau for Nvidia GPUs or
 </li>
 <li>
 <p>
-proprietary driver Nvidia: run ânvidia-settingsâ to
+proprietary driver Nvidia: run <code>nvidia-settings</code> to
                   check that it supports sensors monitoring.
 </p>
 </li>
 <li>
 <p>
-proprietary driver Catalyst/fglx: use âaticonfigâ to
+proprietary driver Catalyst/fglx: use <code>aticonfig</code> to
                   check that it supports sensors monitoring. Important
                   note: it requires that you are using a Psensor
                   binary compiled with the ATI support.
@@ -386,13 +432,26 @@ proprietary driver Catalyst/fglx: use âaticonfigâ to
 </li>
 </ul></div>
 </li>
+</ul></div>
+<div class="paragraph"><p>For hard disk drives, psensor can use:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+udisks2: added since 1.1.2 release. It is the default and
+      recommended provider.
+</p>
+</li>
 <li>
 <p>
-HDDs: it uses the hddtemp daemon. Verifies that it is
-          correctly reporting temperature by using the âsudo hddtemp
-          /dev/sd?â command. If hddtemp does not support your disk,
-          you may want to try using the libatasmart support instead
-          (option âuse-libatasmart option).
+hddtemp: verify that it is correctly reporting temperature by
+      using the command: <code>sudo hddtemp /dev/sda</code>. It is the default
+      provider until 1.1.2 release.
+</p>
+</li>
+<li>
+<p>
+atasmart library: before the 1.1.2 release it can be enabled
+      by using the command line option <code>--use-libatasmart</code>.
 </p>
 </li>
 </ul></div>
@@ -401,6 +460,8 @@ displayed by Psensor, it is probably a bug in Psensor, so please
 report it. Otherwise, the issue is on the underlying software itself
 and you should contact the corresponding development team or refer to
 its documentation.</p></div>
+<div class="paragraph"><p>Since the release 1.1.2, the providers can be enabled or disabled directly
+from the user interface (<code>Preferences&gt;Provider</code>).</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -412,7 +473,7 @@ any Linux distribution.</p></div>
 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
 standard repositories. You have to compile Psensor sensor. You can
-find the instructions in the section âATI/AMD GPU Supportâ of the
+find the instructions in the section <code>ATI/AMD GPU Support</code> of the
 README file available in the Psensor source archives.</p></div>
 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
 compile Psensor with this proprietary library.</p></div>
@@ -453,8 +514,8 @@ the goal of the sensor is to allow the system to
 <p>
 It is only a bug in Psensor if the underlying libraries
           report a different information than Psensor (use the
-          appropriate command or software: âsensorsâ, âaticonfigâ or
-          âhddtempâ to check). In this case, please report a bug.
+          appropriate command or software: <code>sensors</code>, <code>aticonfig</code> or
+          <code>hddtemp</code> to check). In this case, please report a bug.
 </p>
 </li>
 </ul></div>
@@ -471,32 +532,32 @@ starting with:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
-âlmsensor coretempâ: Intel CPU.
+<code>lmsensor coretemp</code>: Intel CPU.
 </p>
 </li>
 <li>
 <p>
-âlmsensor k10tempâ,'lmsensor k8tempâ,'lmsensor fam15h_powerâ: AMD CPU.
+<code>lmsensor k10temp</code>, <code>lmsensor k8temp</code>, <code>lmsensor fam15h_power</code>: AMD CPU.
 </p>
 </li>
 <li>
 <p>
-ânvidiaâ or âlmsensor nouveauâ: NVIDIA GPU.
+<code>nvidia</code> or <code>lmsensor nouveau</code>: NVIDIA GPU.
 </p>
 </li>
 <li>
 <p>
-âhddâ: hard disk drive.
+<code>hdd</code>: hard disk drive.
 </p>
 </li>
 <li>
 <p>
-âamdâ: AMD GPU.
+<code>amd</code>: AMD GPU.
 </p>
 </li>
 <li>
 <p>
-âlmsensor C Bâ: C is the name of the chip, B the name of the adapter.
+<code>lmsensor C B</code>: C is the name of the chip, B the name of the adapter.
 </p>
 </li>
 </ul></div>
@@ -514,37 +575,34 @@ release not available in the standard Ubuntu repositories.</p></div>
 <a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug
 can be reproduced with a package from the standard Ubuntu
 repositories.</p></div>
-<div class="paragraph"><p>If you donât want to use the launchpad, you can send me the report by
-email to <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
-<div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
-please add in its description the output of the command âapt-cache
-policy psensorâ.</p></div>
-<div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
-full output of the âconfigureâ command.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
-<div class="paragraph"><p>If you donât find the information, I am always happy to help, you can
-contact me:</p></div>
+<div class="paragraph"><p>If you donât want to use the launchpad, you can send the report by
+email to:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
-by email: (<a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>), please add â[psensor]â in the
-          subject, I speak English and French.
+<a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a>
 </p>
 </li>
 <li>
 <p>
-or IRC: I am on the #psensor channel of the irc.freenode.net
-          server. My nickname is âjfiâ. Even if I am most of the time
-          connected, I may not be in front of the computer or
-          available, be patient!
+or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.
 </p>
 </li>
 </ul></div>
+<div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
+please add in its description the output of the command: <code>apt-cache
+policy psensor</code>.</p></div>
+<div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
+full output of the <code>configure</code> command.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
+<div class="paragraph"><p>If you donât find the information, you can send an email to the public
+mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> or directly to me:
+<a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -556,13 +614,17 @@ or IRC: I am on the #psensor channel of the irc.freenode.net
 <div class="sect1">
 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Psensor is in the official repository, search âpsensorâ in the software center and install it. More information at: <a href="http://wpitchoune.net/blog/psensor/ubuntu-integration/">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p></div>
+<div class="paragraph"><p>Psensor is in the official repository, search <code>psensor</code> in the
+software center and install it. More information at:
+<a href="http://wpitchoune.net/blog/psensor/ubuntu-integration/">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p></div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Psensor will be in the official repository since Debian 7.0. You can get the last packaged version from the sid repository. More information at: <a href="http://packages.qa.debian.org/p/psensor.html">http://packages.qa.debian.org/p/psensor.html</a>.</p></div>
+<div class="paragraph"><p>Psensor is in the official repository since Debian 7.0. You can get
+the last packaged version from the sid repository. More information
+at: <a href="http://packages.qa.debian.org/p/psensor.html">http://packages.qa.debian.org/p/psensor.html</a>.</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -571,19 +633,19 @@ or IRC: I am on the #psensor channel of the irc.freenode.net
 <div class="ulist"><ul>
 <li>
 <p>
-ppa:jfi/ppa: last stable version.
+<code>ppa:jfi/ppa</code>: last stable version.
 </p>
 </li>
 <li>
 <p>
-ppa:jfi/psensor-unstable: last development version, no major
-          bug is expected.
+<code>ppa:jfi/psensor-unstable</code>: last development version, no
+          major bug is expected.
 </p>
 </li>
 <li>
 <p>
-ppa:jfi/psensor-daily-trunk: build each day directly from
-          the SVN source repository. It may contain major bugs or
+<code>ppa:jfi/psensor-daily-trunk</code>: build each day directly from
+          the GIT source repository. It may contain major bugs or
           incomplete features. Useful for contributors or testing
           whether a bug is fixed.
 </p>
@@ -603,8 +665,8 @@ ppa:jfi/psensor-daily-trunk: build each day directly from
 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
 (since Oneiric) and Debian (since v7) distributions.</p></div>
 <div class="paragraph"><p>For other distributions, you will find the compilation and
-installation instructions in the section âInstallation from source
-archiveâ in the README file of the source archive. Psensor should
+installation instructions in the section <code>Installation from source
+archive</code> in the README file of the source archive. Psensor should
 compile in any modern distribution.</p></div>
 </div>
 </div>
@@ -612,15 +674,65 @@ compile in any modern distribution.</p></div>
 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
-the output of the different commands like sensors.</p></div>
+the output of the different commands like <code>sensors</code>.</p></div>
 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
 0.7.0.4 release it is implemented in both psensor ( menu preferences &gt;
-sensors &gt; enable log of measures) and psensor-server (âsensor-log-file
-option).</p></div>
+sensors &gt; enable log of measures) and psensor-server
+(<code>--sensor-log-file</code> option). For psensor the log file is
+<code>$HOME/.psensor/sensors.log</code>.</p></div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="S_SimilarSoft">14. Is there any other similar softwares?</h2>
+<h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last
+column (named <code>Enabled</code> or <code>Graph</code> depending on the Psensor version).</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_autostart">15. Launch Psensor automaticaly on session startup</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Since the version 1.0.1, Psensor is no more started automaticaly by default.</p></div>
+<div class="paragraph"><p>Open the <code>Preferences</code> window, select the <code>Startup</code> tab and switch on
+the option <code>Launch on session startup</code>.</p></div>
+<div class="paragraph"><p>This feature is requiring that the Desktop Environment supports the
+<a href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
+specification</a>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_disk">16. How to monitor the temperature of a disk with <code>hddtemp</code>?</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Until the release 1.1.2, Psensor is using <code>hddtemp</code> by default to
+retrieve the temperature of the disks.</p></div>
+<div class="paragraph"><p>If <code>hddtemp</code> is installed but no disk temperature is reported, check
+that the daemon is running by using for example the command <code>ps
+-eaf|grep hddtemp</code>.
+It should output something like:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>root      1433     1  0 May28 ?        00:00:21 /usr/sbin/hddtemp -d -l 127.0.0.1 -p 7634 -s | /dev/sdb</code></pre>
+</div></div>
+<div class="paragraph"><p>Depending on the Linux distribution, the installation of the <code>hddtemp</code>
+package does not enable the hddtemp daemon automaticaly.</p></div>
+<div class="paragraph"><p>In this case, edit the file <code>/etc/default/hddtemp</code> and set
+<code>RUN_DAEMON</code> to <code>"true"</code>. After edition, it should contain the
+following line:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>RUN_DAEMON="true"</code></pre>
+</div></div>
+<div class="paragraph"><p>For Debian/Ubuntu, you can use at root:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>dpkg-reconfigure hddtemp</code></pre>
+</div></div>
+<div class="paragraph"><p>and reply <code>yes</code> when asked whether hddtemp daemon must be
+run during the startup.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_SimilarSoft">17. Is there any other similar softwares?</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
 <div class="ulist"><ul>
@@ -648,11 +760,21 @@ more general, but can be configured to display sensors
 </ul></div>
 </div>
 </div>
+<div class="sect1">
+<h2 id="S_HideSensor">18. Is it possible to hide sensors in the main window?</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Before v1.1.1, the sensors retrieved from the lm-sensor library can be
+ignored directly in the lm-sensor configuration. See the manpage
+of sensors.conf(5).</p></div>
+<div class="paragraph"><p>Since v1.1.1, it is possible to hide a sensor, uncheck the setting
+<em>Display sensor in the list of sensors</em> in the sensor preferences.</p></div>
+</div>
+</div>
 </div>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2012-09-15 16:54:46 CEST
+Last updated 2014-10-14 22:59:10 CEST
 </div>
 </div>
 </body>
