Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

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
Comment by Dave Reisner (falconindy) - Friday, 22 June 2012, 21:05 GMT
No, it shouldn't. If you want to override the args, copy the file into /etc/systemd/system and edit it yourself.
Comment by Gaetan Bisson (vesath) - Saturday, 23 June 2012, 01:44 GMT
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.

Loading...