Bug 863986

Summary: RRD Logfile and load-average option cannot be set for sensord
Product: [Fedora] Fedora Reporter: Frank Crawford <frank>
Component: lm_sensorsAssignee: Jaromír Cápík <jcapik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: frank, hdegoede, jcapik, miminar, ovasik, pknirsch
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lm_sensors-3.3.4-10.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-14 08:45:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Crawford 2012-10-08 09:11:40 UTC
Description of problem:
There is no way to set the --rrd-file or --load-average options for sensord can be specified through /etc/sysconfig/sensord

Version-Release number of selected component (if applicable):
lm_sensors-sensord-3.3.2-4.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Inspect /lib/systemd/system/sensord.service
2.
3.
  
Actual results:
Only $INTERVAL and $LOG_INTERVAL are passed to sensord.

Expected results:
A mechanism for specifying general options needs to be added.

Additional info:

Comment 1 Fedora End Of Life 2013-07-03 22:53:31 UTC
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.

Comment 2 Fedora End Of Life 2013-08-01 01:05:20 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Fedora End Of Life 2013-12-21 15:08:18 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.

Comment 4 Jaromír Cápík 2014-01-10 12:48:48 UTC
Hello Frank.

A similar request in scope of Bug 949521 has already been resolved for --rrd-file and --rrd-interval. The RRD file can now be specified, but the --load-average is not implemented yet. I'm going to introduce all the missing switches.

Thanks for the report.

Regards,
Jaromir.

Comment 5 Fedora Update System 2014-01-10 14:03:42 UTC
lm_sensors-3.3.4-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/lm_sensors-3.3.4-10.fc20

Comment 6 Jaromír Cápík 2014-01-10 14:10:00 UTC
Bug 869089 is related ...

Comment 7 Jaromír Cápík 2014-01-10 14:11:04 UTC
(In reply to Jaromír Cápík from comment #6)
> Bug 869089 is related ...

sorry, wrong number ... I meant Bug 949521

Comment 8 Fedora Update System 2014-01-11 08:41:35 UTC
Package lm_sensors-3.3.4-10.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lm_sensors-3.3.4-10.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-0627/lm_sensors-3.3.4-10.fc20
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2014-01-14 08:45:32 UTC
lm_sensors-3.3.4-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.