Red Hat Bugzilla – Bug 817020
numad: variable '-i' can't work fine
Last modified: 2014-01-12 19:01:58 EST
Description of problem:
Depend on numad source code, I know -i options:
numad_log(LOG_NOTICE, "Changing interval to %d:%d\n", msg.body.arg1, msg.body.arg2);
min_interval = msg.body.arg1;
max_interval = msg.body.arg2;
which said msg.body.arg1 is max_interval, msg.body.arg2 is min_interval
but if I set msg.body.arg1 > msg.body.arg2, it still set msg.body.arg1 to min_interval, which caused min_interval > max_interval.
and I have tested it in my box, when I did '# numad -i 10:1',
the log file</var/log/numad.log> show:
Wed Apr 25 15:16:43 2012: Changing interval to 10:1
then the log updated each 1 second, but we expect not 1 second.
and the log should be:
Wed Apr 25 15:16:43 2012: Changing interval to 1:10
maybe the attached patch can fix it.
Created attachment 580765 [details]
fixed '-i' option
I will fix this by enforcing (max >= min), and also fixing man page: it should show min as optional, e.g. -i [min:]max
Thanks for entering the bug report!
*** Bug 818462 has been marked as a duplicate of this bug. ***
Thanks for entering this bug report. This is expected to be fixed in a version pushed upstream (and into Fedora 17?) today (20120523).
New version in F17 should be available in about a week.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Closing: this issue has been fixed and shipped...