On Tue, Sep 22, 2009 at 2:35 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
We've had a few bugs regarding the issue of our crappy default cron.
http://bugs.archlinux.org/task/16085 http://bugs.archlinux.org/task/12910
The consensus among the people who have commented is that fcron is the best bet here.
So let's do this. Would someone like to volunteer to boot our our old crusty dcron in favor of fcron?
On a related note: dcron does not support /etc/cron.d/ and it irritates me to no end. fcron can do this, correct? If not, we should remove the cron.d dir from the package
I was the first one to package the first fcron package to community (however, I did not write the original AUR PKGBUILD). I could take care of it, I don't know how to solve the cron.d problem though, have to look into that.
Note that fcron has been un-updated since December 2007, but it only depends on PAM and has been working perfectly all this time for me. I don't know if the original author still maintains it at all and just had no need to update it, or if he abandoned it. We should maybe determine that.
Another suggestion was vixie-cron - personally I have been using fcron on LFS since 2001 or 2002 and later on Arch, and have been happy with it all those 8 or 9 years. Whatever we do by default, I will keep on using fcron.
It sounds like you're a little hesitant about this. What are our options here? fcron, bcron, vixie-cron?