FS#30408 - [cronie] systemd service file does not obey /etc/conf.d/crond
Attached to Project:
Arch Linux
Opened by Jim Duchek (jimduchek) - Friday, 22 June 2012, 21:03 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 23 June 2012, 01:44 GMT
Opened by Jim Duchek (jimduchek) - Friday, 22 June 2012, 21:03 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 23 June 2012, 01:44 GMT
|
Details
Description:
See title. Service file should have: EnvironmentFile=/etc/conf.d/crond ExecStart=/usr/sbin/crond -n $CRONDARGS Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Gaetan Bisson (vesath)
Saturday, 23 June 2012, 01:44 GMT
Reason for closing: Won't implement
Saturday, 23 June 2012, 01:44 GMT
Reason for closing: Won't implement
Comment by
Dave Reisner (falconindy) - Friday,
22 June 2012, 21:05 GMT
Comment by Gaetan Bisson (vesath) -
Saturday, 23 June 2012, 01:44 GMT
No, it shouldn't. If you want to override the args, copy the file
into /etc/systemd/system and edit it yourself.
Jim: Using /etc/conf.d/ comes in handy with rc.d scripts which are
complex and may only reside in one location. However, as Dave
points out, systemd gives us an easy way to customize units, so
that should be the preferred way.