metalog.conf uses program name "crond" in it's Crond section. http://lists.gentoo.org/pipermail/gentoo-announce/2002-April/000151.html suggests that dcron is the Gentoo default, and that has a "crond". http://www.gentoo.org/doc/en/gentoo-x86-install.xml suggests using vcron, and that has a "cron" instead. It also recommends metalog. So if you use the recommended metalog and vcron together, you get cron messages only in /var/log/everything/, not /var/log/crond. I found that a little surprising. Not sure what (if anything) to do about it. Perhaps metalog's ebuild file should warn you to change metalog.conf if you use it with vcron?
From what I can see: dcron = crond fcron = fcron vcron = cron So the only cron that will work out-o-the-box is dcron, while the other two need .conf adjustments in metalog. I'm wondering if it might do some good to switch: program = "crond" to: facility = "cron" in metalog.conf. That should cover capture of all cron messages regardless of which cron is being used.
Sounds good to me; I've changed my metalog.conf accordingly. You might also consider using: logdir = "/var/log/cron" instead of: logdir = "/var/log/crond" although I could imagine such a change could cause some confusion.
Wow this bug has been idling around for a long time. I've got facility = "cron" in my config, and I use vcron fine. I'll try to find out if it works with d/fcron too.
Ok, this change is committed to CVS. Vcron and fcron work with facility, and I couldn't get dcron to log to syslog. If dcron does log to syslog, but not using the cron facility, then its got the problem.
