Hi ! I just had a little trouble the last days, while trying to install a new server. Used to dcron, I decided to use vixie-cron, which seemed to be a more complete implementation of the cron daemon. I just emerged vixie-cron, without any problem. Launched it too, no problem. And then, I imported my template crontab, used for ages with dcron, without any problem. One of the lines in this crontab looks like : 00 05 * * * emerge --sync Classical... But : no way to make it work with vixie-cron. No error in logs, nothing ! I searched for a quite (very) long time, but finished to understand what was happening : PATH was fixed, in the beginning of the crontab, to : PATH=/bin:/usr/bin:/sbin:/usr/sbin But, /usr/bin/emerge is just a symbolic link to /usr/lib/portage/bin/emerge ! And, therefore, vixie-cron refuses to run the script, where dcron just does it fine ! To correct this behaviour, I had to modify the PATH line as follows : PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/portage/bin/ And, at least, this worked ! This is not really a bug, but this made me waste a lot of time. Since I don't know how the devs usually deal with such "problems", I didn't modify anything. But maybe just a line added to pkg_postinst could help users with this package ? Or, even better, a commented line in the system crontab : /etc/crontab ?
*** This bug has been marked as a duplicate of bug 53934 ***
