The main difference between running from the command line and from cron is
that your .profile doesn't get sourced when you run from cron.
Adding $DBI::errstr to your error message would make the message from
Fatal() more meaningful.
--
Mac :})
** I may forward private database questions to the DBI mail lists. **
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll eat fish for an age.
----- Original Message -----
From: "James Maes" <[EMAIL PROTECTED]>
To: "DBI" <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 6:08 PM
Subject: weird runtime error problems w/ dbi
> informix 9.2uc1
> DBI 1.13
> DBD 0.97005
> RH linux 6.2
>
>
> here is my connection line.
>
> $dbh =
>
DBI->connect("dbi:Informix:$database_config->{server}",$database_config->{us
ername},$database_config->{password},{RaiseError=>0,AutoCommit=>0,PrintError
=>1})
> || $self->Fatal("couldn't connect to database: '$database'");
>
>
> Here is my problem. Scripts will run fine, and skip over errors withour
> dieing when ran from the command line. However, when the same script is
> running from cron, the script will die() on a error from dbi.
