Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
Help! Let command not found in cron job
Name: John Toh Date: December 19, 2001 at 08:19:59 Pacific
Comment:
Hi Everyone,
I had an urgent problem here... Supposedly I create the following script:-
Running the above script at the unix prompt is alright but when i schedule it to run in cronjobs, there will always be an error message "let : not found"
I actually tried applying different paths on the above but still failed!
Name: oliver Date: December 19, 2001 at 12:29:20 Pacific
Reply:
what shell does the user who runs this cron job have? If it's root, then root has bourne shell where "let" is not recognised. Try running it as a regular user through cron
0
Response Number 2
Name: John Toh Date: December 19, 2001 at 18:37:27 Pacific
Reply:
Help...
I tried with a regular user instead of root but still failed.... why is that it always prompt me for this problem "let: not found"????
Help deeply appreciated
0
Response Number 3
Name: Anthony Foot Date: December 20, 2001 at 04:49:27 Pacific
Reply:
Hello, It is down to the shell, it appears to not recognising you are trying to run it under the korn shell. The line #!/usr/bin/ksh is it the very first line of the program? If not then it will not force your shell into korn shell (ksh). You must have no comments nor blank lines before it.
Summary: Dear my future friends, I am doing tests at home with a Ultra 60, Solaris 8 (End User). In my program *.csh, one line is: setenv a b the returned message is: setenv: not found In my office, I do not...
Summary: Hi, I want to run a crontab job. I have configured the crontab accordingly 10 * * * * /scripts/dbalter.pl >> /scripts/cronout.txt.However this does not work .Then I go to /var/mail/root and find an er...
Summary: I don't have a definitive answer for you, but I have some observations: 1) Note that where chmod is working it runs in 1 second. Where it fails the command runs for 51 seconds. That's rather a long...