On Thu, 25.11.10 19:57, Genes MailLists (lists(a)sapience.com) wrote:
> Although I can't be the only one who puts various cron jobs
> under /etc/cron.d that get run at various times.
Almost every administrative cron here is in a cron.d crontab file .. we
need control over exactly what time certain things happen. So please
keep the functionality.
Hey, as I made explcitily clear I have no plans of taking away anything
from you. No need to be defensive...
If systemd is the expert spawner - then perhaps things like cron (or
any reproductive daemon for that matter) could lean on a systemd for
spawn service - but leave the other application specific parts to the
local daemons to do for themselves.
There is some merit in functional separation too ...
Well, there isn't if the remaining bits simply do some minimal calendar
calculations and do that in a way we shouldn't do things anymore, and
hence needs to be fixed anyway.
As mentioned: i have no plans to take crond away. Just change it to be
started a little bit differently.
Lennart Poettering - Red Hat, Inc.