Bug 1440479

Summary: systemd presets request - thermald
Product: [Fedora] Fedora Reporter: Björn Esser (besser82) <besser82>
Component: fedora-releaseAssignee: Dennis Gilmore <dennis>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dennis, fedora, jdisnard, jforbes, kellin, kevin, labbott, mboddu, sgallagh, sgraf, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-26 15:16:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Björn Esser (besser82) 2017-04-09 10:00:25 UTC 
* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?

  No, works out-of-the-box.


* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?

  No, it's running without any need for networking.


* Is the service non-persistent (i.e. run once at startup and exit)?

  It's a persistent daemon controlling CPU temperature and throttle.


* What is the exact name (or names) of the systemd unit files to be enabled?

  thermald.service


* Is this request for all Fedora deliverables or only for some Editions (list them)?

  Request is for all deliverables, starting from F26.
Comment 1 Kevin Fenzi 2017-04-09 16:26:56 UTC 
I'm kind of leary of enabling this sort of service by default. It seems to me like it's papering over bugs in the kernel that we should fix in the kernel. 

Is it possible to configure in a way that would damage your machine(s)? ie, looks like you can tell it to take over completely from the kernel thermal core and also tell it to only use passive, might this not result in problems?

Also might result in more kernel maintainer burden (If someone is using this and reports thermal problems it might take some back and forth to notice it's overriding the kernel here.)
Comment 2 Stephen Gallagher 2017-04-10 12:19:19 UTC 
I'm going to recommend we take this to FESCo for discussion. I think there's probably an oversight in the default service policy. I think there's a strong argument to be made that services should not be enabled by preset if its behavior significantly changes the behavior of another service on the system.

Or, in other words: this service sounds to me like something that the user should have to enable intentionally rather than automatically.
Comment 3 Justin M. Forbes 2017-04-26 15:14:30 UTC 
As it was discussed in the FESCo meeting on 2017-04-21, it was agreed that the thermald service should not be enabled by default.
Comment 4 Justin M. Forbes 2017-04-26 15:15:16 UTC 
Forgot to link the FESCo ticket for further information:

https://pagure.io/fesco/issue/1698
Comment 5 Björn Esser (besser82) 2017-04-26 15:16:02 UTC 
Okie, closing here.