-
Notifications
You must be signed in to change notification settings - Fork 27
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
fans warning/critical logic broken (?) #10
Comments
- code simplified and cleaned up XXX: The threshold logic for warning/critical messages seems broken but I'm not sure how it was intended to work. See: nikband#10
Yes the logic it's not so simple (and i hope correct) and there are no check of input thresholds. In my real nagios i have done some test fans 2400 2200 fans 2500 2400 Let me know if it's ok and if you help me to write this in more corret english and logical way you are welcome thanks In this period i m busy with work... but i don-t forget the plugin |
OK, thank you for explanation, it's clear now. I've been looking into the script and trying to fix issues I've discovered. You can see my commits in my clone of your repo. I have not changed output or functionality (yet) in order not to break compatibility. Let me know what you think please. |
I added a check to make sure users get it right (that is |
Hi. It's not clear to me what should warning & critical thresholds mean for fans RPMs.
Are they supposed to be lower bounds, meaning that a fan should not spin slower?
Or are they supposed to be upper bounds, meaning that a fan should not spin faster?
Either way the current logic seems to be broken and does not do what I expect.
Can you check and confirm please ? ... Thanks.
The text was updated successfully, but these errors were encountered: