Thanks Kevin.  That did the trick.  I didn't have vcron in my default run
level.  I could have sworn I had done this, but I guess I didn't.

Ran the rc-update command, and did a /etc/init.d/vcron start, and things
started happening right...

Shawn

-----Original Message-----
From: Kevin Anderson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 4:52 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: (clug-talk) Cron not working?


If this is a Gentoo box, did you rc-update add the appropriate cron daemon
to the default runlevel?  ls -alh should show a link inside
/etc/runlevels/default.  On my system, I'm using vcron, so there's a vcron
entry there.  You'll see similar problems if this hasn't been added.

Otherwise, it looks right.  crontab -e is used to edit the cron table, so
you're using the right command to put things in there.  crontab -l lists the
contents of the current cron table, and crontab -r removes it entirely.  -r
is a stupid option I'd say, but then cron was thought up by smarter people
than me, so whatever...

Kev.

Reply via email to