From: "Paul B. Henson" <henson@acm.org>
To: <gentoo-dev@lists.gentoo.org>, <cron-bugs@gentoo.org>
Subject: RE: [gentoo-dev] Recommend cronie instead of vixie-cron in handbook?
Date: Tue, 10 Dec 2013 18:18:08 -0800 [thread overview]
Message-ID: <0afb01cef617$3d667a90$b8336fb0$@acm.org> (raw)
In-Reply-To: <1386708905.1931.2.camel@belkin5>
> From: Pacho Ramos [mailto:pacho@gentoo.org]
> Sent: Tuesday, December 10, 2013 12:55 PM
>
> This has reminded me that maybe we should switch to cronie from
> vixie-cron as default and recommended cron provider in Handbook. Last
> time I checked, vixie-cron upstream was died while cronie forked it
> fixing some bugs :/
>
> What do you think?
I'd say go one step further and get rid of vixie-cron completely, is there anything it does that cronie can't do as well or better? It's getting pretty crusty, with a lot of open bugs that haven't been resolved. While updating the handbook might get new users to use a better cron, masking vixie-cron (and perhaps a news item?) could get existing users to migrate to a supported and maintained cron as well…
next prev parent reply other threads:[~2013-12-11 2:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 20:55 [gentoo-dev] Recommend cronie instead of vixie-cron in handbook? Pacho Ramos
2013-12-10 21:33 ` Lars Wendler
2013-12-10 21:41 ` Jeff Horelick
2013-12-11 2:18 ` Paul B. Henson [this message]
2013-12-11 19:25 ` Michael Orlitzky
2013-12-11 20:03 ` Mike Gilbert
2013-12-13 22:15 ` Dale
2013-12-14 17:19 ` Michael Orlitzky
2013-12-24 3:54 ` Vadim A. Misbakh-Soloviov
2013-12-24 4:02 ` Michael Orlitzky
2013-12-25 6:38 ` Alice Ferrazzi
2013-12-25 14:43 ` [gentoo-dev] " Duncan
2013-12-27 4:02 ` Daniel Campbell
2013-12-27 6:56 ` Duncan
2013-12-11 19:22 ` [gentoo-dev] " Sven Vermeulen
2013-12-11 19:30 ` Peter Stuge
2013-12-11 21:07 ` Alexander Tsoy
2013-12-11 22:02 ` Ben Kohler
2013-12-11 20:20 ` Markos Chandras
2013-12-11 21:07 ` Peter Stuge
2013-12-11 22:13 ` Wulf C. Krueger
2013-12-13 13:45 ` Sergey Popov
2013-12-13 16:08 ` Peter Stuge
2013-12-13 16:17 ` Ben Kohler
2013-12-13 16:53 ` Brian Dolbec
2013-12-13 19:11 ` Markos Chandras
2013-12-14 23:13 ` Peter Stuge
2013-12-15 18:51 ` Maciej Mrozowski
2013-12-16 18:39 ` Michał Górny
2013-12-29 8:45 ` Sergey Popov
2013-12-11 23:42 ` Pavlos Ratis
2013-12-12 9:23 ` Lars Wendler
2013-12-14 15:55 ` [gentoo-dev] " Steven J. Long
2013-12-12 10:34 ` [gentoo-dev] " Ultrabug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0afb01cef617$3d667a90$b8336fb0$@acm.org' \
--to=henson@acm.org \
--cc=cron-bugs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox