Closed bennaux closed 4 years ago
I've tried to call it tempsource.sh
as well, with no effects...
What am I doing wrong?
Hey, Thanks for the bug report. This is indeed a somewhat untainted feature. It was relevant when s-tui was only displaying a single temperature sensor. Now that it displays all, I'm not sure how to build the feature so the alert will only fire for a specific sensor, for for several.
Maybe it would be possible to split it up somehow?
A minimal approach could be to just compare max(sensor1, sensor2, ...) with the threshold.
Indeed, the minimal approach is what we'll use for now.
I've pushed a fix and and update for the readme. The file indeed needs to be called tempsource.sh
.
Regardless, a fix was needed to correctly respect the passed parameters for the threshold temperature (-tt
)
I pushed a fix in version 1.0.2. Please verify. Thank you
Thank you very much -- I do not have any machine to verify it at the moment, but I will have one in a few months and try it. :-)
Step 1: Describe your environment
Step 2: Describe the problem:
I've placed a file
~/.config/s-tui/hooks.d/temperaturesource.sh
:Made it executable:
chmod +x ~/.config/s-tui/hooks.d/temperaturesource.sh
And invoked s-tui like this:
Started
stress
:The temperatures shoot right over the given 40 degrees, but the stress command always terminates itself after the 20 seconds and is not killed by the threshold script.