This is a common problem when running from crontab. Cron gets a minimal environment. It is up to you to set the environment so that the job will run.
Some folks do it by sourcing .profile in the script. I don't care for that, as modifications to .profile may then break the job. One method to do it is dump your whole env into a file, edit the file to remove stuff you know you don't need, and then source that from the script. You need to do this as the user that will be running the cronjob. eg. $> env > ~/.cron_profile in your script source the .cron_profile . ~/.cron_profile HTH Jared On 1/26/06, Daniel Castro <[EMAIL PROTECTED]> wrote: > > Hi, > > When I run : > dbmcli -d HE -u DBM,DBM -uUTL -c backup_start completeF > > From the prompt it works fine, but when i run it from crontab nothing > happens. > THere is no message also. > Can you help me? > -- > Daniel Castro > Website: http://danielti.no-ip.info:2139 > MSN: [EMAIL PROTECTED] > Skype: danielti2005 > ICQ : 316727989 > Jabber: danielti > Linux User: 387864 > AOL User: Danielti2005 > Sola Scriptura, Sola Gratia, Sola Fide, Solus Christus, Soli Deo Gloria > > -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist
