Quote:
Ok. For a cron job the required profile must be set so that the script executes.
Now how do we tell cron that it has to execute the script with this profile
|
Is not true.
Not loading the .profile does not "stop" a cronjob from executing. It may be that without it the job will not work, but that's not the same thing.
If your script produces output it will (normally) go to your mailbox if it's set up. Check your mail to see if there are any errors.
A common cause (apart from the
daemon not running) of cronjobs not running is that too many jobs are running and new jobs are queued up and the
daemon can't start them
Code:
/var/log/cron
or
/var/adm/log/cron
or
somewhere else depending on your OS
should report if this is the case.
