Closed Bug 53716 Opened 24 years ago Closed 24 years ago

whineatnews.pl says command not found when run from crontab

Categories

(Bugzilla :: Bugzilla-General, defect, P3)

Other
Other
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: bg.mahesh, Assigned: justdave)

Details

hi My crontab reads, 0 1 * * * `cd /home/bugs/public_html/; ./whineatnews.pl` > /dev/null 0 2 * * * `cd /home/bugs/public_html/; ./collectstats.pl` > /dev/null If I run this command from command line, bugs(2)% cd /home/bugs/public_html/;./whineatnews.pl /home/bugs/public_html xyz@team.indiainfo.com 3 4 5 6 7 abc@team.indiainfo.com 1 2 But when the same command is run from crontab, I get an email which reads, From: root@oracle.indiainfo.com (Cron Daemon) To: bugs@oracle.indiainfo.com Subject: Cron <bugs@oracle> `cd /home/bugs/public_html/; ./whineatnews.pl` > /dev/null X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/bugs> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=bugs> /bin/sh: abc@team.indiainfo.com: command not found ---- actually the shell of "bugs" account is /bin/tcsh
try removing the quotes from around your command line in the crontab entry. (or extend them to include the redirection to /dev/null). The semicolon indications a new command line, but the quotes make it group with the first command instead.
whineatnews.pl spits out the email address of each person it whines to. by having backticks around the command line, you're executing the contents of the standard out from that command. drop the backticks. :)
No reply from reporter, resolving INVALID.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
True, the backticks are the reason for the error message. Verified invalid.
Status: RESOLVED → VERIFIED
moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.