* 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.
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.)
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.
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.
Forgot to link the FESCo ticket for further information: https://pagure.io/fesco/issue/1698
Okie, closing here.