Koentje wrote: ⤴Sun Nov 19, 2023 8:49 pm
Then in your conky change this part:
${execi 10 sensors | grep 'Core 0' | awk {'print $3'}}
into this:
${execpi 10 ./check-cpu-temp.sh}
Notice the
p in exec
pi. That pastes the output of the bash script into your conky window.
Let me know if it worked for you.
Thanks for all the replies. I can't say I followed all of the discussion. I am first of all trying to get the first solution from Koentje working. I created the text file as shown, chmod 755 then added this line to my conky
${execpi 10 .conky/check-cpu-temp.sh}
( only difference being that I
think it is in .conky/). If I understand the code this should at least have produced some output even "No temp1 found".
Koentje, your amplified solution of reading hwmon settings at start seems the best way since it will, I presume, lead to a conky that will work universally (?). Unfortunately my linux knowledge is not advanced enough to know what this means:
Code: Select all
In my case i run a script at boot time that checks all hwmon folders and output their names with path to /etc/hwmon
Bash script
Code: Select all
###########################################################
# #
# Checks which hwmon path belongs to which chipset name #
# #
# Run at boot via rc.local #
# #
Script I can manage but where to put it, how it should be chmodded and what does run at boot via rc.local mean? Perhaps this is a step too far.
My installed conky is
conky 1.12.2 compiled 2022-02-23 for Linux x86_64
.
dollyp
LinuxMint 21.2 Cinnamon 5.8.4