crontab

[Bob Smith]

The other thing that you need to do is to check any environment and path 
requirements that your application requires.  When cron runs a job, the 
path that it provides is minimal, as are most of the environment 
variables.  You may want to consider enclosing your application in a 
script file, setting your environment variables there, and handling all 
of your logging within the script.  This way you can see where your 
application is failing, other than looking in root's mail.

-Bob

Rodolfo J. Paiz wrote:

> At 08:53 PM 6/27/2004, Muhammad Rizwan Khan wrote:
>
>> I am trying to add following entry in crontab, with this command 
>> crontab -e
>> 0 23 * * * /root/MyApplication
>
>
>         1. You are typing "crontab -e" while being logged in as root, 
> right?
>
>         2. You are aware that this job will run *only* at 11:00pm 
> every night?
>
>         3. The cron service is running, right? (Check "service crond 
> status".)
>
> Cheers,
>
>