The 2004.0 LiveCD started just a few minutes after boot an updatedb. I guess, it's not needed on a LiveCD. Furthermore I think all cron-activities should be stopped at boot-time.
If I'm not mistaken the only one who has this enabled is the kde/gnome livecd for G4. The others don't have this. Pieter
I'm not sure, because vapier murmured something, that other LiveCDs (not only ppc related) have also this issue... Maybe he can enlighten us ;-)
i said it happened on the g4 livecd to me ... but i mentioned that perhaps it's not arch specific ... personally i dont see why crontab should be enabled/included at all on the livecd
If I'm not mistaken I enabled it on gerks request who was running the livecd for a few days on some of his machines. If logs didn't got rotated, they would fill up valuable ram. Like I said, my script added vcron to default runlevel, but vcron moved to vixie-cron, so it didn't get added to the default runlevel. Which reminds me our docs need updating, vcron no longer exists and emerge vcron fails.
very good point, that didnt occur to me ;) updatedb though should definitely not be included in the crontab setup
removed for 2004.0 - this seems to be the case for all architectures now with catalyst. Have added a remark about adding services to catalyst in catalyst/REMARKS, so it is possible to build a custom livecd with a crontab added.
