1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
\r
6 <meta name="generator" content="AsciiDoc 8.6.9" />
\r
7 <title>Psensor Frequently Asked Questions</title>
\r
8 <style type="text/css">
\r
11 background: #e2e2e2;
\r
13 font-family: Ubuntu,Arial,sans-serif;
\r
15 font-weight: lighter;
\r
16 margin: 1em 2em 2em 2em;
\r
22 margin: 0 0 0.267em 0;
\r
24 font-weight: normal;
\r
29 margin: 0 0 0.375em;
\r
31 font-weight: normal;
\r
36 margin: 0 0 0.522em;
\r
38 font-weight: normal;
\r
43 margin: 0 0 0.615em;
\r
45 font-weight: normal;
\r
56 font-weight: normal;
\r
58 letter-spacing: 0.1em;
\r
59 margin: 0 0 0.923em;
\r
60 text-transform: uppercase;
\r
80 text-decoration: none;
\r
84 text-decoration: underline;
\r
88 font-family: "Ubuntu Mono","Courier New",Courier,monospace;
\r
89 font-weight: normal;
\r
94 background: none repeat scroll 0 0 #e0e0e0;
\r
96 padding: 0.5em 0.5em;
\r
98 white-space: pre-wrap;
\r
99 word-wrap: break-word;
\r
110 font-weight: lighter;
\r
121 background: #ffffff;
\r
123 -moz-box-sizing: border-box;
\r
125 padding: 2em 2em 2em 2em;
\r
127 -moz-border-radius: 4px;
\r
128 -webkit-border-radius: 4px;
\r
129 border-radius: 4px;
\r
131 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
132 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
136 background: #ffffff;
\r
137 -moz-box-sizing: border-box;
\r
138 padding: 2em 2em 2em 2em;
\r
140 -moz-border-radius: 4px;
\r
141 -webkit-border-radius: 4px;
\r
142 border-radius: 4px;
\r
144 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
145 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
148 #menu-list, #menu-list > li > ul {
\r
149 list-style-type: none;
\r
152 /* menu on left col, content on right col */
\r
167 margin: 0em 0em 2em 0em;
\r
169 background: #ffffff;
\r
170 -moz-box-sizing: border-box;
\r
171 padding: 2em 2em 2em 2em;
\r
173 -moz-border-radius: 4px;
\r
174 -webkit-border-radius: 4px;
\r
175 border-radius: 4px;
\r
177 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
178 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
183 <script type="text/javascript">
\r
185 var asciidoc = { // Namespace.
\r
187 /////////////////////////////////////////////////////////////////////
\r
188 // Table Of Contents generator
\r
189 /////////////////////////////////////////////////////////////////////
\r
191 /* Author: Mihai Bazon, September 2002
\r
192 * http://students.infoiasi.ro/~mishoo
\r
194 * Table Of Content generator
\r
197 * Feel free to use this script under the terms of the GNU General Public
\r
198 * License, as long as you do not remove or alter this notice.
\r
201 /* modified by Troy D. Hanson, September 2006. License: GPL */
\r
202 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
\r
204 // toclevels = 1..4.
\r
205 toc: function (toclevels) {
\r
207 function getText(el) {
\r
209 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
210 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
\r
212 else if (i.firstChild != null)
\r
213 text += getText(i);
\r
218 function TocEntry(el, text, toclevel) {
\r
221 this.toclevel = toclevel;
\r
224 function tocEntries(el, toclevels) {
\r
225 var result = new Array;
\r
226 var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
\r
227 // Function that scans the DOM tree for header elements (the DOM2
\r
228 // nodeIterator API would be a better technique but not supported by all
\r
230 var iterate = function (el) {
\r
231 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
232 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
\r
233 var mo = re.exec(i.tagName);
\r
234 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
\r
235 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
\r
245 var toc = document.getElementById("toc");
\r
250 // Delete existing TOC entries in case we're reloading the TOC.
\r
251 var tocEntriesToRemove = [];
\r
253 for (i = 0; i < toc.childNodes.length; i++) {
\r
254 var entry = toc.childNodes[i];
\r
255 if (entry.nodeName.toLowerCase() == 'div'
\r
256 && entry.getAttribute("class")
\r
257 && entry.getAttribute("class").match(/^toclevel/))
\r
258 tocEntriesToRemove.push(entry);
\r
260 for (i = 0; i < tocEntriesToRemove.length; i++) {
\r
261 toc.removeChild(tocEntriesToRemove[i]);
\r
264 // Rebuild TOC entries.
\r
265 var entries = tocEntries(document.getElementById("content"), toclevels);
\r
266 for (var i = 0; i < entries.length; ++i) {
\r
267 var entry = entries[i];
\r
268 if (entry.element.id == "")
\r
269 entry.element.id = "_toc_" + i;
\r
270 var a = document.createElement("a");
\r
271 a.href = "#" + entry.element.id;
\r
272 a.appendChild(document.createTextNode(entry.text));
\r
273 var div = document.createElement("div");
\r
274 div.appendChild(a);
\r
275 div.className = "toclevel" + entry.toclevel;
\r
276 toc.appendChild(div);
\r
278 if (entries.length == 0)
\r
279 toc.parentNode.removeChild(toc);
\r
283 /////////////////////////////////////////////////////////////////////
\r
284 // Footnotes generator
\r
285 /////////////////////////////////////////////////////////////////////
\r
287 /* Based on footnote generation code from:
\r
288 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
\r
291 footnotes: function () {
\r
292 // Delete existing footnote entries in case we're reloading the footnodes.
\r
294 var noteholder = document.getElementById("footnotes");
\r
298 var entriesToRemove = [];
\r
299 for (i = 0; i < noteholder.childNodes.length; i++) {
\r
300 var entry = noteholder.childNodes[i];
\r
301 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
\r
302 entriesToRemove.push(entry);
\r
304 for (i = 0; i < entriesToRemove.length; i++) {
\r
305 noteholder.removeChild(entriesToRemove[i]);
\r
308 // Rebuild footnote entries.
\r
309 var cont = document.getElementById("content");
\r
310 var spans = cont.getElementsByTagName("span");
\r
313 for (i=0; i<spans.length; i++) {
\r
314 if (spans[i].className == "footnote") {
\r
316 var note = spans[i].getAttribute("data-note");
\r
318 // Use [\s\S] in place of . so multi-line matches work.
\r
319 // Because JavaScript has no s (dotall) regex flag.
\r
320 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
\r
321 spans[i].innerHTML =
\r
322 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
\r
323 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
324 spans[i].setAttribute("data-note", note);
\r
326 noteholder.innerHTML +=
\r
327 "<div class='footnote' id='_footnote_" + n + "'>" +
\r
328 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
\r
329 n + "</a>. " + note + "</div>";
\r
330 var id =spans[i].getAttribute("id");
\r
331 if (id != null) refs["#"+id] = n;
\r
335 noteholder.parentNode.removeChild(noteholder);
\r
337 // Process footnoterefs.
\r
338 for (i=0; i<spans.length; i++) {
\r
339 if (spans[i].className == "footnoteref") {
\r
340 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
\r
341 href = href.match(/#.*/)[0]; // Because IE return full URL.
\r
343 spans[i].innerHTML =
\r
344 "[<a href='#_footnote_" + n +
\r
345 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
351 install: function(toclevels) {
\r
354 function reinstall() {
\r
355 asciidoc.footnotes();
\r
357 asciidoc.toc(toclevels);
\r
361 function reinstallAndRemoveTimer() {
\r
362 clearInterval(timerId);
\r
366 timerId = setInterval(reinstall, 500);
\r
367 if (document.addEventListener)
\r
368 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
\r
370 window.onload = reinstallAndRemoveTimer;
\r
374 asciidoc.install(2);
\r
378 <body class="article">
\r
380 <h1>Psensor Frequently Asked Questions</h1>
\r
382 <div id="toctitle">Table of Contents</div>
383 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
387 <div id="preamble">
\r
388 <div class="sectionbody">
\r
389 <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
392 <div class="sect1">
\r
393 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
\r
394 <div class="sectionbody">
\r
395 <div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
\r
396 <div class="ulist"><ul>
\r
399 motherboard and CPUs sensors: the information is retrieved
\r
400 from the lm-sensors library, it requires that
\r
401 <code>sensors-detect</code> has been run and the kernel module
\r
402 correctly installed. <code>sensors</code> can be used for checking.
\r
407 GPUs: it depends on which driver you are using:
\r
409 <div class="ulist"><ul>
\r
412 Opensource drivers (nouveau for Nvidia GPUs or
\r
413 radeon/ati for ATI GPUs) is used and support sensor
\r
414 monitoring for your GPU, the information is using
\r
415 lm-sensors, same steps than above.
\r
420 proprietary driver Nvidia: run <code>nvidia-settings</code> to
\r
421 check that it supports sensors monitoring.
\r
426 proprietary driver Catalyst/fglx: use <code>aticonfig</code> to
\r
427 check that it supports sensors monitoring. Important
\r
428 note: it requires that you are using a Psensor
\r
429 binary compiled with the ATI support.
\r
436 HDDs: it uses the hddtemp daemon. Verify that it is
\r
437 correctly reporting temperature by using the command: <code>sudo
\r
438 hddtemp /dev/sda</code>. If hddtemp does not support your disk,
\r
439 you may want to try using the libatasmart support instead
\r
440 (option <code>--use-libatasmart</code>).
\r
444 <div class="paragraph"><p>If the underlying software is reporting sensors which are not
\r
445 displayed by Psensor, it is probably a bug in Psensor, so please
\r
446 report it. Otherwise, the issue is on the underlying software itself
\r
447 and you should contact the corresponding development team or refer to
\r
448 its documentation.</p></div>
\r
451 <div class="sect1">
\r
452 <h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>
\r
453 <div class="sectionbody">
\r
454 <div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor
\r
455 must be compiled with a proprietary library which is not packaged in
\r
456 any Linux distribution.</p></div>
\r
457 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
\r
458 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
\r
459 standard repositories. You have to compile Psensor sensor. You can
\r
460 find the instructions in the section <code>ATI/AMD GPU Support</code> of the
\r
461 README file available in the Psensor source archives.</p></div>
\r
462 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
\r
463 compile Psensor with this proprietary library.</p></div>
\r
466 <div class="sect1">
\r
467 <h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>
\r
468 <div class="sectionbody">
\r
469 <div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower
\r
470 than the ambiant temperature, negative, higher than the sun
\r
471 temperature, etc):</p></div>
\r
472 <div class="ulist"><ul>
\r
475 most of the time it is not a bug in Psensor nor in the
\r
476 underlying monitoring libraries:
\r
478 <div class="ulist"><ul>
\r
481 if the temperature does not change, it might be due
\r
482 to an existent sensor not wired by the hardware
\r
488 the goal of the sensor is to allow the system to
\r
489 detect critical temperature and NOT to report an
\r
490 exact temperature. Most sensors report a relative
\r
491 temperature. The more it differs from the critical
\r
492 temperature , the more it is wrong.
\r
499 It is only a bug in Psensor if the underlying libraries
\r
500 report a different information than Psensor (use the
\r
501 appropriate command or software: <code>sensors</code>, <code>aticonfig</code> or
\r
502 <code>hddtemp</code> to check). In this case, please report a bug.
\r
508 <div class="sect1">
\r
509 <h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>
\r
510 <div class="sectionbody">
\r
511 <div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on
\r
512 its name in the main window and select the menu item Preferences), and
\r
513 look at the Chip field.</p></div>
\r
514 <div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is
\r
515 starting with:</p></div>
\r
516 <div class="ulist"><ul>
\r
519 <code>lmsensor coretemp</code>: Intel CPU.
\r
524 <code>lmsensor k10temp</code>, <code>lmsensor k8temp</code>, <code>lmsensor fam15h_power</code>: AMD CPU.
\r
529 <code>nvidia</code> or <code>lmsensor nouveau</code>: NVIDIA GPU.
\r
534 <code>hdd</code>: hard disk drive.
\r
539 <code>amd</code>: AMD GPU.
\r
544 <code>lmsensor C B</code>: C is the name of the chip, B the name of the adapter.
\r
548 <div class="paragraph"><p>For more information about lmsensor devices, see
\r
549 <a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>
\r
552 <div class="sect1">
\r
553 <h2 id="S_BugReport">5. How to report a bug?</h2>
\r
554 <div class="sectionbody">
\r
555 <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
556 even if it can only reproduced with a non-Ubuntu distribution or a
\r
557 release not available in the standard Ubuntu repositories.</p></div>
\r
558 <div class="paragraph"><p>You can also use
\r
559 <a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug
\r
560 can be reproduced with a package from the standard Ubuntu
\r
561 repositories.</p></div>
\r
562 <div class="paragraph"><p>If you don’t want to use the launchpad, you can send the report by
\r
563 email to:</p></div>
\r
564 <div class="ulist"><ul>
\r
567 <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
568 <a href="https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users</a>)
\r
573 or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.
\r
577 <div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
\r
578 please add in its description the output of the command: <code>apt-cache
\r
579 policy psensor</code>.</p></div>
\r
580 <div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
\r
581 full output of the <code>configure</code> command.</p></div>
\r
584 <div class="sect1">
\r
585 <h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
\r
586 <div class="sectionbody">
\r
587 <div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
\r
588 <div class="paragraph"><p>If you don’t find the information, you can send an email to the public
\r
589 mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
590 <a href="https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users</a>)
\r
591 or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
\r
594 <div class="sect1">
\r
595 <h2 id="S_Contribute">7. How to contribute?</h2>
\r
596 <div class="sectionbody">
\r
597 <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
600 <div class="sect1">
\r
601 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
\r
602 <div class="sectionbody">
\r
603 <div class="paragraph"><p>Psensor is in the official repository, search <code>psensor</code> in the
\r
604 software center and install it. More information at:
\r
605 <a href="http://wpitchoune.net/blog/psensor/ubuntu-integration/">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p></div>
\r
608 <div class="sect1">
\r
609 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
\r
610 <div class="sectionbody">
\r
611 <div class="paragraph"><p>Psensor is in the official repository since Debian 7.0. You can get
\r
612 the last packaged version from the sid repository. More information
\r
613 at: <a href="http://packages.qa.debian.org/p/psensor.html">http://packages.qa.debian.org/p/psensor.html</a>.</p></div>
\r
616 <div class="sect1">
\r
617 <h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>
\r
618 <div class="sectionbody">
\r
619 <div class="ulist"><ul>
\r
622 <code>ppa:jfi/ppa</code>: last stable version.
\r
627 <code>ppa:jfi/psensor-unstable</code>: last development version, no
\r
628 major bug is expected.
\r
633 <code>ppa:jfi/psensor-daily-trunk</code>: build each day directly from
\r
634 the GIT source repository. It may contain major bugs or
\r
635 incomplete features. Useful for contributors or testing
\r
636 whether a bug is fixed.
\r
642 <div class="sect1">
\r
643 <h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>
\r
644 <div class="sectionbody">
\r
645 <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
648 <div class="sect1">
\r
649 <h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>
\r
650 <div class="sectionbody">
\r
651 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
\r
652 (since Oneiric) and Debian (since v7) distributions.</p></div>
\r
653 <div class="paragraph"><p>For other distributions, you will find the compilation and
\r
654 installation instructions in the section <code>Installation from source
\r
655 archive</code> in the README file of the source archive. Psensor should
\r
656 compile in any modern distribution.</p></div>
\r
659 <div class="sect1">
\r
660 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
\r
661 <div class="sectionbody">
\r
662 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
\r
663 the output of the different commands like <code>sensors</code>.</p></div>
\r
664 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
\r
665 0.7.0.4 release it is implemented in both psensor ( menu preferences >
\r
666 sensors > enable log of measures) and psensor-server
\r
667 (<code>--sensor-log-file</code> option).</p></div>
\r
670 <div class="sect1">
\r
671 <h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>
\r
672 <div class="sectionbody">
\r
673 <div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last
\r
674 column (named <code>Enabled</code> or <code>Graph</code> depending on the Psensor version).</p></div>
\r
677 <div class="sect1">
\r
678 <h2 id="S_autostart">15. Launch Psensor automaticaly on session startup</h2>
\r
679 <div class="sectionbody">
\r
680 <div class="paragraph"><p>Since the version 1.0.1, Psensor is no more started automaticaly by default.</p></div>
\r
681 <div class="paragraph"><p>Open the <code>Preferences</code> window, select the <code>Startup</code> tab and switch on
\r
682 the option <code>Launch on session startup</code>.</p></div>
\r
683 <div class="paragraph"><p>This feature is requiring that the Desktop Environment supports the
\r
684 <a href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
\r
685 specification</a>.</p></div>
\r
688 <div class="sect1">
\r
689 <h2 id="S_disk">16. How to monitor the temperature of a disk?</h2>
\r
690 <div class="sectionbody">
\r
691 <div class="paragraph"><p>By default, Psensor is using <code>hddtemp</code> to retrieve the temperature of
\r
692 the disks.</p></div>
\r
693 <div class="paragraph"><p>If <code>hddtemp</code> is installed but no disk temperature is reported, check
\r
694 that the daemon is running by using for example the command <code>ps
\r
695 -eaf|grep hddtemp</code>.
\r
696 It should output something like:</p></div>
\r
697 <div class="listingblock">
\r
698 <div class="content">
\r
699 <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
701 <div class="paragraph"><p>Since recent Ubuntu releases, installing the <code>hddtemp</code> package is not
\r
702 enough, it is required to manually allow the <code>hddtemp</code> daemon. Edit the
\r
703 file <code>/etc/default/hddtemp</code> and set <code>RUN_DAEMON</code> to <code>"true"</code>.</p></div>
\r
704 <div class="listingblock">
\r
705 <div class="content">
\r
706 <pre><code># hddtemp network daemon switch. If set to true, hddtemp will listen
\r
707 # for incoming connections.
\r
708 RUN_DAEMON="true"</code></pre>
\r
712 <div class="sect1">
\r
713 <h2 id="S_SimilarSoft">17. Is there any other similar softwares?</h2>
\r
714 <div class="sectionbody">
\r
715 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
\r
716 <div class="ulist"><ul>
\r
719 for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>
\r
724 for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>
\r
729 for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>
\r
734 more general, but can be configured to display sensors
\r
735 information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>
\r
742 <div id="footnotes"><hr /></div>
\r
744 <div id="footer-text">
\r
745 Last updated 2014-08-04 09:16:55 CEST
\r