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:
Created attachment 561298 [details] Native systemd service for sensord
does this work in systemd ${INTERVAL:+-i $INTERVAL} ?
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.
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...