Monitoring hardware in KDE (4.9 up) [Solved]

[linuxfluesterer]

Hallo Fitzcarraldo...
It's a cross... I did, like you and other instructions said, I made

Code: Select all

# rc-update add hddtemp default

And my hddtemp program was and is running (checked with)

Code: Select all

# rc-update show -v | grep hddtemp
              hddtemp |      default                                 
# rc-status default | grep hddtemp
 hddtemp                                                           [  started  ]
#

But the GKrellM still shows only cpu1, cpu2 and gpu temperature, no hdd temperature.
And I can not mark any hdd sensor in setting (not show for mark).
When I then stop GKrellM, and then start hddtemp as root and after it start GKrellM in Alt-F2-Window,
then I see a new empty sensor field for hddtemp/sda. I must mark it.

Then I see the hdd temperature displayed in GKrellM also.
So, when I mark it, I see sda temperature in just that moment, when I click 'ok'.

I think, that GKrellM options don't remember hddtemp settings in temperature configure settings.
And ... the Oxygen System Monitor is much more beautiful. I still don't know, why there is NO temperature shown...

Hmmmmm.

Good evening,

-Linuxfluesterer (I love KDE ...)

[linuxfluesterer]

Hallo Fitzcarraldo.
Sorry for late reply to your last message and suggesstions. In last days I helped a friend to install SL X KDE.
To come to an end with my topic, I will give you my last experiences here.
These are the steps:
1. When Boot, hddtemp deamon is started as default (I've checked with rc-update show|grep hddtemp).
2. Boot comes up, after login GKrellM is started by 'Autostart' (I never used GKrellMd)
3. But no hdd settings possible to set in GKrellM
4. So, close GKrellM, start hddtemp, start GKrellM
5. Now I can set hddtemp mark, then I see sda temperature.
My solution:
When don't autostart GKrellM, next boot GKrellM is not started, so:
8. Start GKrellM manually with KRunner, then everything is fine, I see sda temperature

I assume, GKrellM is called too early after hddtemp (or any other module necessary).

For the moment, I would close that topic for 50%, because I can help myself manually.
You agree or you have another idea?

Anyway, thank you (again) for your help,

-Linuxfluesterer (I love KDE ...)

[Fitzcarraldo]

Sure. But there is one other thing I would try just for interest. Try adding a delay in the /etc/local.d/01hddtemp.start file:

Code: Select all

#!/bin/bash
hddtemp && sleep 10s

Code: Select all

chmod +x /etc/local.d/01hddtemp.start

Or, alternatively, add the delay before the gkrellm command in a Bash script in the Autostart directory that launches GKrellM.

[linuxfluesterer]

Sure. But there is one other thing I would try just for interest. Try adding a delay in the /etc/local.d/01hddtemp.start file:

Code: Select all

#!/bin/bash
hddtemp && sleep 10s

I tried like you said, but with same result like before.
So I tried your other suggestion:

Or, alternatively, add the delay before the gkrellm command in a Bash script in the Autostart directory that launches GKrellM.

Code: Select all

#!/bin/bash
# Start the gkrellm command with delay
sleep 120
/usr/bin/gkrellm


Now, it may take a long time until gkrellm is started, but now it is correct.

I assume, the point of importance is after Login in KDE.
Maybe I can shorten the sleep time, but in essence, that way works.
Thank you again, Fitzcarraldo.

Good evening,

-Linuxfluesterer (I love KDE ...)