Ksensors still not working with hddtemp for normal users

I am attaching a workaround to this bug which avoids the unpleasantness of setuid-ing the hddtemp binary. The idea: to place a small bash script in the users private bin directory, with the same name as the hddtemp binary. This script invokes "netcat localhost 7634" to get the raw hard drive temperature info from the hddtemp daemon, parses this data, and outputs it in exactly the same format used by hddtemp. When ksensors invokes "hddtemp", this script gets executed instead of the real hddemp binary. It's simple and it works!

Thanks Dario,
I can confirm this bug. No HDD temperature was displayed before I used the script.
However, when I use your script, I get six times the same hard disk displayed. I do have six SATA slots, but only four of them are used. Also, all six readings are exactly the same. Same temperature and same label. Any idea what might be causing this? I had to wget your script. Swiftweasel added a funny character after the degree sign at the end of the script.

I wrote a script of my own that can handle mutli hard drive systems.
It is in Perl. Works fine on my machine. You may do with it whatever you want, but don't blame me if your PC melts when running it ;D .
There is still one issue though, at start, Ksensors does not detect correctly the HDD's names. So you have to rename them by hand :( .

It kind of stinks that KSensors is deprecated, as in it has been developed or worked on in 3 years. Another option is to check out Kima in the mean time.

Whatever Debian did to the parsing last year may have caused the issue. I will look into it a little more here. Thanks everyone for your scripts and ideas.

AHH! KSensors ran as root works like a charm :) Anyone know of the dangers in doing so?

OK, I just got done speaking with the developer of KSensors.

As for running KSensors as root, this is a bad thing.

As for doing the SUID trick on HDTemp, this is not such a bad thing.

His recommendation was to run 'dpkg-reconfigure hdtemp' and when asked if you want to suid hdtemp, you should go ahead and do so.

So, now the question is, is this a KSensors issue or is it a HDTemp issue?

I am going to transfer this over as a "hddtemp" bug now as it isn't KSensors fault for hddtemp not running or configured to run with SUID root, which after speaking with the developers, is a safer alternative than running KSensors as root in order for this to work. The current work around is listed in the post just previous to this one. Thank you!