+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"\r
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
-<head>\r
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 8.6.9" />\r
-<title>Psensor Frequently Asked Questions</title>\r
-<style type="text/css">\r
-\r
-body {\r
- background: #e2e2e2;\r
- color: #333333;\r
- font-family: Ubuntu,Arial,sans-serif;\r
- line-height: 1.6;\r
- font-weight: lighter;\r
- margin: 1em 2em 2em 2em;\r
- padding: 0 0 0 0;\r
-}\r
-\r
-h1 {\r
- font-size: 2.813em;\r
- margin: 0 0 0.267em 0;\r
- padding: 0 0 0 0;\r
- font-weight: normal;\r
-}\r
-\r
-h2 {\r
- font-size: 2em;\r
- margin: 0 0 0.375em;\r
- padding: 0 0 0 0;\r
- font-weight: normal;\r
-}\r
-\r
-h3 {\r
- font-size: 1.438em;\r
- margin: 0 0 0.522em;\r
- padding: 0 0 0 0;\r
- font-weight: normal;\r
-}\r
-\r
-h4 {\r
- font-size: 1.219em;\r
- margin: 0 0 0.615em;\r
- padding: 0 0 0 0;\r
- font-weight: normal;\r
-}\r
-\r
-h5 {\r
- font-size: 1em;\r
- margin: 0 0 0.75em;\r
- padding: 0 0 0 0;\r
- font-weight: bold;\r
-}\r
-\r
-h6 {\r
- font-weight: normal;\r
- font-size: 0.813em;\r
- letter-spacing: 0.1em;\r
- margin: 0 0 0.923em;\r
- text-transform: uppercase;\r
- padding: 0 0 0 0;\r
-}\r
-\r
-li {\r
- margin: 0 0 0 1em;\r
- line-height: 1.6;\r
-}\r
-\r
-li p {\r
- margin: 0 0 0 0;\r
-}\r
-\r
-ul {\r
- margin: 0 0 0 0;\r
- padding: 0 0 0 0;\r
-}\r
-\r
-a:link, a:visited {\r
- color: #19B6EE;\r
- text-decoration: none;\r
-}\r
-\r
-a:hover {\r
- text-decoration: underline;\r
-}\r
-\r
-code, pre, tt {\r
- font-family: "Ubuntu Mono","Courier New",Courier,monospace;\r
- font-weight: normal;\r
- color: #333333;\r
-}\r
-\r
-pre {\r
- background: none repeat scroll 0 0 #e0e0e0;\r
- border-radius: 4px;\r
- padding: 0.5em 0.5em;\r
- margin: 0 0 0 0;\r
- white-space: pre-wrap;\r
- word-wrap: break-word;\r
-}\r
-\r
-table {\r
- width: 100%;\r
- text-align: left;\r
-}\r
-\r
-#footer {\r
- margin: 0 0 0 0;\r
- font-size: 0.8em;\r
- font-weight: lighter;\r
- clear: both;\r
- text-align: right;\r
-}\r
-\r
-#page {\r
- margin: 0 0 0 0;\r
- padding: 0 0 0 0;\r
-}\r
-\r
-#main {\r
- background: #ffffff;\r
-\r
- -moz-box-sizing: border-box;\r
-\r
- padding: 2em 2em 2em 2em;\r
-\r
- -moz-border-radius: 4px;\r
- -webkit-border-radius: 4px;\r
- border-radius: 4px;\r
-\r
- -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;\r
- box-shadow: 0 2px 2px 0 #C2C2C2;\r
-}\r
-\r
-#menu {\r
- background: #ffffff;\r
- -moz-box-sizing: border-box;\r
- padding: 2em 2em 2em 2em;\r
-\r
- -moz-border-radius: 4px;\r
- -webkit-border-radius: 4px;\r
- border-radius: 4px;\r
-\r
- -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;\r
- box-shadow: 0 2px 2px 0 #C2C2C2;\r
-}\r
-\r
-#menu-list, #menu-list > li > ul {\r
- list-style-type: none;\r
-}\r
-\r
-/* menu on left col, content on right col */\r
-\r
-#menu {\r
- float: left;\r
- width: 18%;\r
-}\r
-\r
-#main {\r
- float: right;\r
- width: 80%;\r
-}\r
-\r
-/* asciidoc */\r
-\r
-#toc, #content {\r
- margin: 0em 0em 2em 0em;\r
-\r
- background: #ffffff;\r
- -moz-box-sizing: border-box;\r
- padding: 2em 2em 2em 2em;\r
-\r
- -moz-border-radius: 4px;\r
- -webkit-border-radius: 4px;\r
- border-radius: 4px;\r
-\r
- -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;\r
- box-shadow: 0 2px 2px 0 #C2C2C2;\r
-}\r
-\r
-\r
-</style>\r
-<script type="text/javascript">\r
-/*<+'])');\r
- // Function that scans the DOM tree for header elements (the DOM2\r
- // nodeIterator API would be a better technique but not supported by all\r
- // browsers).\r
- var iterate = function (el) {\r
- for (var i = el.firstChild; i != null; i = i.nextSibling) {\r
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {\r
- var mo = re.exec(i.tagName);\r
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {\r
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);\r
- }\r
- iterate(i);\r
- }\r
- }\r
- }\r
- iterate(el);\r
- return result;\r
- }\r
-\r
- var toc = document.getElementById("toc");\r
- if (!toc) {\r
- return;\r
- }\r
-\r
- // Delete existing TOC entries in case we're reloading the TOC.\r
- var tocEntriesToRemove = [];\r
- var i;\r
- for (i = 0; i < toc.childNodes.length; i++) {\r
- var entry = toc.childNodes[i];\r
- if (entry.nodeName.toLowerCase() == 'div'\r
- && entry.getAttribute("class")\r
- && entry.getAttribute("class").match(/^toclevel/))\r
- tocEntriesToRemove.push(entry);\r
- }\r
- for (i = 0; i < tocEntriesToRemove.length; i++) {\r
- toc.removeChild(tocEntriesToRemove[i]);\r
- }\r
-\r
- // Rebuild TOC entries.\r
- var entries = tocEntries(document.getElementById("content"), toclevels);\r
- for (var i = 0; i < entries.length; ++i) {\r
- var entry = entries[i];\r
- if (entry.element.id == "")\r
- entry.element.id = "_toc_" + i;\r
- var a = document.createElement("a");\r
- a.href = "#" + entry.element.id;\r
- a.appendChild(document.createTextNode(entry.text));\r
- var div = document.createElement("div");\r
- div.appendChild(a);\r
- div.className = "toclevel" + entry.toclevel;\r
- toc.appendChild(div);\r
- }\r
- if (entries.length == 0)\r
- toc.parentNode.removeChild(toc);\r
-},\r
-\r
-\r
-/////////////////////////////////////////////////////////////////////\r
-// Footnotes generator\r
-/////////////////////////////////////////////////////////////////////\r
-\r
-/* Based on footnote generation code from:\r
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html\r
- */\r
-\r
-footnotes: function () {\r
- // Delete existing footnote entries in case we're reloading the footnodes.\r
- var i;\r
- var noteholder = document.getElementById("footnotes");\r
- if (!noteholder) {\r
- return;\r
- }\r
- var entriesToRemove = [];\r
- for (i = 0; i < noteholder.childNodes.length; i++) {\r
- var entry = noteholder.childNodes[i];\r
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")\r
- entriesToRemove.push(entry);\r
- }\r
- for (i = 0; i < entriesToRemove.length; i++) {\r
- noteholder.removeChild(entriesToRemove[i]);\r
- }\r
-\r
- // Rebuild footnote entries.\r
- var cont = document.getElementById("content");\r
- var spans = cont.getElementsByTagName("span");\r
- var refs = {};\r
- var n = 0;\r
- for (i=0; i<spans.length; i++) {\r
- if (spans[i].className == "footnote") {\r
- n++;\r
- var note = spans[i].getAttribute("data-note");\r
- if (!note) {\r
- // Use [\s\S] in place of . so multi-line matches work.\r
- // Because JavaScript has no s (dotall) regex flag.\r
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];\r
- spans[i].innerHTML =\r
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +\r
- "' title='View footnote' class='footnote'>" + n + "</a>]";\r
- spans[i].setAttribute("data-note", note);\r
- }\r
- noteholder.innerHTML +=\r
- "<div class='footnote' id='_footnote_" + n + "'>" +\r
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +\r
- n + "</a>. " + note + "</div>";\r
- var id =spans[i].getAttribute("id");\r
- if (id != null) refs["#"+id] = n;\r
- }\r
- }\r
- if (n == 0)\r
- noteholder.parentNode.removeChild(noteholder);\r
- else {\r
- // Process footnoterefs.\r
- for (i=0; i<spans.length; i++) {\r
- if (spans[i].className == "footnoteref") {\r
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");\r
- href = href.match(/#.*/)[0]; // Because IE return full URL.\r
- n = refs[href];\r
- spans[i].innerHTML =\r
- "[<a href='#_footnote_" + n +\r
- "' title='View footnote' class='footnote'>" + n + "</a>]";\r
- }\r
- }\r
- }\r
-},\r
-\r
-install: function(toclevels) {\r
- var timerId;\r
-\r
- function reinstall() {\r
- asciidoc.footnotes();\r
- if (toclevels) {\r
- asciidoc.toc(toclevels);\r
- }\r
- }\r
-\r
- function reinstallAndRemoveTimer() {\r
- clearInterval(timerId);\r
- reinstall();\r
- }\r
-\r
- timerId = setInterval(reinstall, 500);\r
- if (document.addEventListener)\r
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);\r
- else\r
- window.onload = reinstallAndRemoveTimer;\r
-}\r
-\r
-}\r
-asciidoc.install(2);\r
-/*]]>*/\r
-</script>\r
-</head>\r
-<body class="article">\r
-<div id="header">\r
-<h1>Psensor Frequently Asked Questions</h1>\r
-<div id="toc">
- <div id="toctitle">Table of Contents</div>
- <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
-</div>\r
-</div>\r
-<div id="content">\r
-<div id="preamble">\r
-<div class="sectionbody">\r
-<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>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the\r
-information about the computer:</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-motherboard and CPUs sensors: the information is retrieved\r
- from the lm-sensors library, it requires that\r
- <code>sensors-detect</code> has been run and the kernel module\r
- correctly installed. <code>sensors</code> can be used for checking.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-GPUs: it depends on which driver you are using:\r
-</p>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-Opensource drivers (nouveau for Nvidia GPUs or\r
- radeon/ati for ATI GPUs) is used and support sensor\r
- monitoring for your GPU, the information is using\r
- lm-sensors, same steps than above.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-proprietary driver Nvidia: run <code>nvidia-settings</code> to\r
- check that it supports sensors monitoring.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-proprietary driver Catalyst/fglx: use <code>aticonfig</code> to\r
- check that it supports sensors monitoring. Important\r
- note: it requires that you are using a Psensor\r
- binary compiled with the ATI support.\r
-</p>\r
-</li>\r
-</ul></div>\r
-</li>\r
-</ul></div>\r
-<div class="paragraph"><p>For hard disk drives, psensor can use:</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-udisks2: added since 1.1.2 release. It is the default and\r
- recommended provider.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-hddtemp: verify that it is correctly reporting temperature by\r
- using the command: <code>sudo hddtemp /dev/sda</code>. It is the default\r
- provider until 1.1.2 release.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-atasmart library: before the 1.1.2 release it can be enabled\r
- by using the command line option <code>--use-libatasmart</code>.\r
-</p>\r
-</li>\r
-</ul></div>\r
-<div class="paragraph"><p>If the underlying software is reporting sensors which are not\r
-displayed by Psensor, it is probably a bug in Psensor, so please\r
-report it. Otherwise, the issue is on the underlying software itself\r
-and you should contact the corresponding development team or refer to\r
-its documentation.</p></div>\r
-<div class="paragraph"><p>Since the release 1.1.2, the providers can be enabled or disabled directly\r
-from the user interface (<code>Preferences>Provider</code>).</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor\r
-must be compiled with a proprietary library which is not packaged in\r
-any Linux distribution.</p></div>\r
-<div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a\r
-compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian\r
-standard repositories. You have to compile Psensor sensor. You can\r
-find the instructions in the section <code>ATI/AMD GPU Support</code> of the\r
-README file available in the Psensor source archives.</p></div>\r
-<div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to\r
-compile Psensor with this proprietary library.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower\r
-than the ambiant temperature, negative, higher than the sun\r
-temperature, etc):</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-most of the time it is not a bug in Psensor nor in the\r
- underlying monitoring libraries:\r
-</p>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-if the temperature does not change, it might be due\r
- to an existent sensor not wired by the hardware\r
- manufacturer.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-the goal of the sensor is to allow the system to\r
- detect critical temperature and NOT to report an\r
- exact temperature. Most sensors report a relative\r
- temperature. The more it differs from the critical\r
- temperature , the more it is wrong.\r
-</p>\r
-</li>\r
-</ul></div>\r
-</li>\r
-<li>\r
-<p>\r
-It is only a bug in Psensor if the underlying libraries\r
- report a different information than Psensor (use the\r
- appropriate command or software: <code>sensors</code>, <code>aticonfig</code> or\r
- <code>hddtemp</code> to check). In this case, please report a bug.\r
-</p>\r
-</li>\r
-</ul></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on\r
-its name in the main window and select the menu item Preferences), and\r
-look at the Chip field.</p></div>\r
-<div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is\r
-starting with:</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-<code>lmsensor coretemp</code>: Intel CPU.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>lmsensor k10temp</code>, <code>lmsensor k8temp</code>, <code>lmsensor fam15h_power</code>: AMD CPU.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>nvidia</code> or <code>lmsensor nouveau</code>: NVIDIA GPU.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>hdd</code>: hard disk drive.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>amd</code>: AMD GPU.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>lmsensor C B</code>: C is the name of the chip, B the name of the adapter.\r
-</p>\r
-</li>\r
-</ul></div>\r
-<div class="paragraph"><p>For more information about lmsensor devices, see\r
-<a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_BugReport">5. How to report a bug?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Please use <a href="https://bugs.launchpad.net/psensor/+filebug">https://bugs.launchpad.net/psensor/+filebug</a> to report bugs\r
-even if it can only reproduced with a non-Ubuntu distribution or a\r
-release not available in the standard Ubuntu repositories.</p></div>\r
-<div class="paragraph"><p>You can also use\r
-<a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug\r
-can be reproduced with a package from the standard Ubuntu\r
-repositories.</p></div>\r
-<div class="paragraph"><p>If you don’t want to use the launchpad, you can send the report by\r
-email to:</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-<a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a>\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.\r
-</p>\r
-</li>\r
-</ul></div>\r
-<div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,\r
-please add in its description the output of the command: <code>apt-cache\r
-policy psensor</code>.</p></div>\r
-<div class="paragraph"><p>If it is related to the Psensor source compilation, please add the\r
-full output of the <code>configure</code> command.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>\r
-<div class="paragraph"><p>If you don’t find the information, you can send an email to the public\r
-mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> or directly to me:\r
-<a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_Contribute">7. How to contribute?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>See <a href="http://wpitchoune.net/blog/psensor/how-to-contribute/">http://wpitchoune.net/blog/psensor/how-to-contribute/</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Psensor is in the official repository, search <code>psensor</code> in the\r
-software center and install it. More information at:\r
-<a href="http://wpitchoune.net/blog/psensor/ubuntu-integration/">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Psensor is in the official repository since Debian 7.0. You can get\r
-the last packaged version from the sid repository. More information\r
-at: <a href="http://packages.qa.debian.org/p/psensor.html">http://packages.qa.debian.org/p/psensor.html</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>\r
-<div class="sectionbody">\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-<code>ppa:jfi/ppa</code>: last stable version.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>ppa:jfi/psensor-unstable</code>: last development version, no\r
- major bug is expected.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-<code>ppa:jfi/psensor-daily-trunk</code>: build each day directly from\r
- the GIT source repository. It may contain major bugs or\r
- incomplete features. Useful for contributors or testing\r
- whether a bug is fixed.\r
-</p>\r
-</li>\r
-</ul></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>See <a href="http://aur.archlinux.org/packages.php?ID=37807">http://aur.archlinux.org/packages.php?ID=37807</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu\r
-(since Oneiric) and Debian (since v7) distributions.</p></div>\r
-<div class="paragraph"><p>For other distributions, you will find the compilation and\r
-installation instructions in the section <code>Installation from source\r
-archive</code> in the README file of the source archive. Psensor should\r
-compile in any modern distribution.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_LOG">13. How to log sensors temperatures?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>The best way is probably to use sensord or a custom script based on\r
-the output of the different commands like <code>sensors</code>.</p></div>\r
-<div class="paragraph"><p>Anyway, as I received several requests about such feature, since the\r
-0.7.0.4 release it is implemented in both psensor ( menu preferences >\r
-sensors > enable log of measures) and psensor-server\r
-(<code>--sensor-log-file</code> option). For psensor the log file is\r
-<code>$HOME/.psensor/sensors.log</code>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last\r
-column (named <code>Enabled</code> or <code>Graph</code> depending on the Psensor version).</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_autostart">15. Launch Psensor automaticaly on session startup</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Since the version 1.0.1, Psensor is no more started automaticaly by default.</p></div>\r
-<div class="paragraph"><p>Open the <code>Preferences</code> window, select the <code>Startup</code> tab and switch on\r
-the option <code>Launch on session startup</code>.</p></div>\r
-<div class="paragraph"><p>This feature is requiring that the Desktop Environment supports the\r
-<a href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG\r
-specification</a>.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_disk">16. How to monitor the temperature of a disk with <code>hddtemp</code>?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Until the release 1.1.2, Psensor is using <code>hddtemp</code> by default to\r
-retrieve the temperature of the disks.</p></div>\r
-<div class="paragraph"><p>If <code>hddtemp</code> is installed but no disk temperature is reported, check\r
-that the daemon is running by using for example the command <code>ps\r
--eaf|grep hddtemp</code>.\r
-It should output something like:</p></div>\r
-<div class="listingblock">\r
-<div class="content">\r
-<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>\r
-</div></div>\r
-<div class="paragraph"><p>Depending on the Linux distribution, the installation of the <code>hddtemp</code>\r
-package does not enable the hddtemp daemon automaticaly.</p></div>\r
-<div class="paragraph"><p>In this case, edit the file <code>/etc/default/hddtemp</code> and set\r
-<code>RUN_DAEMON</code> to <code>"true"</code>. After edition, it should contain the\r
-following line:</p></div>\r
-<div class="listingblock">\r
-<div class="content">\r
-<pre><code>RUN_DAEMON="true"</code></pre>\r
-</div></div>\r
-<div class="paragraph"><p>For Debian/Ubuntu, you can use at root:</p></div>\r
-<div class="listingblock">\r
-<div class="content">\r
-<pre><code>dpkg-reconfigure hddtemp</code></pre>\r
-</div></div>\r
-<div class="paragraph"><p>and reply <code>yes</code> when asked whether hddtemp daemon must be\r
-run during the startup.</p></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_SimilarSoft">17. Is there any other similar softwares?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>\r
-<div class="ulist"><ul>\r
-<li>\r
-<p>\r
-for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-more general, but can be configured to display sensors\r
- information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>\r
-</p>\r
-</li>\r
-</ul></div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="S_HideSensor">18. Is it possible to hide sensors in the main window?</h2>\r
-<div class="sectionbody">\r
-<div class="paragraph"><p>Before v1.1.1, the sensors retrieved from the lm-sensor library can be\r
-ignored directly in the lm-sensor configuration. See the manpage\r
-of sensors.conf(5).</p></div>\r
-<div class="paragraph"><p>Since v1.1.1, it is possible to hide a sensor, uncheck the setting\r
-<em>Display sensor in the list of sensors</em> in the sensor preferences.</p></div>\r
-</div>\r
-</div>\r
-</div>\r
-<div id="footnotes"><hr /></div>\r
-<div id="footer">\r
-<div id="footer-text">\r
-Last updated\r
- 2016-06-05 13:12:53 CEST\r
-</div>\r
-</div>\r
-</body>\r
-</html>\r
projects / psensor-pkg-debian.git / blobdiff