Right, my man pages call the sixth argument command, it's the whole thing /usr/bin/perl -w /Users/.../CronTest.pl.
First, please check /var/log/messages or /var/log/warn (maybe there is someting in /var/adm/ too, it depends on the OS) if something suspicious happened around 08:19-08:21. It is AFIK important that your crontab file ends with a linefeed but not with an empty line! So please check that too.
How does your Perl program displays that it has done something? Does it create a file or a log-entry? Do not expect to see something in your terminal or in your X window (you can redirect console though). If your program sends something to STDOUT or STDERR, you'll usually get an e-mail. So have a look at /var/spool/mail/myname (or the location where your system locally stores e-mails). For further experiments, I suggest to use a simple cron-command like /bin/date >> /tmp/mycrontabcheck.txt. Each time, your cronjob is executed, it is documented in /tmp/mycrontabcheck.txt
I would be surprised if your cron-daemon is not running..., however ps -elf | grep cron | grep root should come up with something like /usr/sbin/cron or ...crond.
Security: man crontab explains what you have to do regarding the /etc/cron.allow and /etc/cron.deny issues better than I can do here, but shortly: if /etc/cron.allow exists, your UID (myname?) must be a single linefeed terminated line in this file. If this file does not exist, your UID must not be listed in /etc/cron.deny (neither: ALL).
In reply to Re^5: Running a perl script automatically on Mac OS X 10.5
by Perlbotics
in thread Running a perl script automatically on Mac OS X 10.5
by Ninth Prince
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |