Bug 789761

Summary: Provide native systemd service
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: lm_sensorsAssignee: Nikola Pajkovsky <npajkovs>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dhoward, hdegoede, npajkovs, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-13 13:42:59 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:
Bug Depends On:    
Bug Blocks: 751869    
Attachments:
Description Flags
Native systemd service for sensord none

Description Jóhann B. Guðmundsson 2012-02-12 21:00:20 UTC 
Description of problem:

Let's get the ball rolling on this one...

http://fedoraproject.org/wiki/Features/SysVtoSystemd
https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jóhann B. Guðmundsson 2012-02-12 21:00:58 UTC 
Created attachment 561298 [details]
Native systemd service for sensord
Comment 2 Nikola Pajkovsky 2012-02-13 12:42:36 UTC 
does this work in systemd ${INTERVAL:+-i $INTERVAL} ?
Comment 3 Jóhann B. Guðmundsson 2012-02-13 12:50:33 UTC 
Hmm not without escaping to shell. 

What or rather why exactly do you need it?

Systemd has time units not sure if it's applicable in this case but you should have a look at man systemd.timer and if applicable we could create an sensord.time unit for it there.
Comment 4 Jóhann B. Guðmundsson 2012-02-13 12:54:38 UTC 
I should mention that Environment files like /etc/sysconfig/foo are Fedora/Red Hat specific so upstream wont accept that unit if you put it in there and submit it upstream since it's not cross distro usable. 

I also should mention that using environment files like /etc/sysconfig/foo is deprecated.

Administrators should follow this procedure http://fedoraproject.org/wiki/Systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F These days...