-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperature threshold is not run #151
Comments
I've tried to call it What am I doing wrong? |
Hey, |
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. |
* Fixes for #157 and #158 - Fix summaries not saved, taking info from graphs - Remove clock when no stress tool is installed * Check if psutil traits return not none Fix for #154 * Only check not none if attr exists * Filter non-sane values * Always add a counter indecator for repeating sensors * Fix for #151 no call for hook
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.
The text was updated successfully, but these errors were encountered: