Here is what I use for a perl script I use to restart the oracle
listener if it goes down, to set the oracle environment.

 

00,10,20,30,40,50 * * * * (. $HOME/.bash_profile;
$HOME/hdpjfw_scripts/dbping.pl) >$HOME/spool/db_ping.out 2>&1

 

________________________________

From: Mazhar [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 11, 2006 11:05 AM
To: Beginner
Cc: beginners perl
Subject: Re: Perl Script as a Cron Job

 

 

On 10/11/06, Beginner <[EMAIL PROTECTED]> wrote: 

On 11 Oct 2006 at 17:14, Mazhar wrote:

> From the help above i created a new perl code and i was successfull in

> running the code by typing the command /scripts/newxxx.pl but the same
is
> not executed by cron i have the cron entry as below
>
>  10 * * * * /scripts/newxxx.pl


This as to be the longest running thread since the great "Good 
answer/bad answer" debate.

So Mazhar:

1) In who's crontab file have you put this entry?
2) Does this user exist in cron-allow?
3) Do you need to HUP crond to get the cron -rescheduled?
4) Have you any access to the cron log, if so what does that say? 
5) Try printing out the environment variables at the start of the
script incase there is something restricting the job. Something like
the bit below (untested).

foreach my $k (%ENV) {
       print "$k -> $ENV{$k}\n"; 
}


Is there any any output from the command, either from cron or from
the command line? Can we see a sample please and the output from the
above.
Thanx.
Dp.


--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
< http://learn.perl.org/ <http://learn.perl.org/> >
<http://learn.perl.org/first-response>




Dear DP,

 

Your answers to the questions above are here as follows,

 

1) In who's crontab file have you put this entry?

  In Root Login
2) Does this user exist in cron-allow?

 Yes 
3) Do you need to HUP crond to get the cron -rescheduled?

No
4) Have you any access to the cron log, if so what does that say?

How can i found the log file for cron job

 

5) Try printing out the environment variables at the start of the
script incase there is something restricting the job. Something like
the bit below (untested).

foreach my $k (%ENV) {
       print "$k -> $ENV{$k}\n"; 
}

Attached is the file containing the output of the above script (op.log)

 

Regards

Mazhar

Reply via email to