Shell Programming and Scripting

Yes, I do want the command executed - that is intended.
the mail_report variable will have output that looks like this:

Code:

nbdeployutil --report /usr/openv/var/global/reports/20140104_044802_servername

The command is a two part command. Step one is just to run
nbdeployutil --gather
That will run for a length of time and generate several different files in a specified directory. It also spits out some output that looks like this:

Code:

NetBackup Deployment Utility, version 6.5.6_EEB1_PET2269969_SET2269958
Gathering license deployment information...
  Discovered master server servername
  Output for servername at: /usr/openv/var/global/reports/20140105_002630_servername
Gather DONE
Execution time: 15 secs
To create a report for this master server, run the following:
  nbdeployutil --report /usr/openv/var/global/reports/20140105_002630_servername

I cut out the necessary part (the part that stays "run the following") and assign it to the mail_report variable and then execute it since it is the second step of the command to run to give me the final report.

This works interactively using the script, but not through cron.

You said that PATH doesn't matter. You said that when using cron, PATH is defined by:

Code:

PATH=/usr/sbin:/usr/bin

Is nbdeployutil in /usr/sbin or in /usr/bin? Or is it in /usr/openv/netbackup/bin or one of its subdirectories that is in your PATH when you run it in an environment where it works successfully?

You said your script uses absolute pathnames for everything it executes. But, nbdeployutil is not an absolute pathname.

Hi Don, in this case I am using full paths in the script so the PATH environment variable doesn't come into play here. Further, the script works up to this line. I am able to tell this because the second temp file is never updated and the output file is never created. I think cron doesn't like this line

Code:

/bin/echo `$mail_report` > /tmp/nbdeployutil_temp_rpt.out

which works fine under the interactive shell.

No, no, no! The PATH environment variable absolutely DOES COME INTO PLAY here. Using back quotes (shown in red above) asks the shell being run by cron to execute the command found between those quotes. The shell has to find that command in one of the directories specified by $PATH to be able to execute it unless you use an absolute pathname. The nbdeployutil in the command you are asking the shell to execute:

Code:

nbdeployutil --report /usr/openv/var/global/reports/20140104_044802_servername

is not an absolute pathname and is not found in the directories listed in the PATH setting that is being used when you run this script under cron!

If you want this script to work under cron, you either need to change the way you set mail_report so it includes an absolute pathname for nbdeployutil or you need to set PATH so the shell being run by cron will be able to find nbdeployutil in one of the directories named in $PATH as it is set in cron's environment.

Holy moly, Don! I hadn't even given that any thought (obviously)! I will give that a try and let you know, but I'm feeling pretty good that this is the issue!

Hi,

Could you please help me out in scheduling a mail through Unix command.
I am using "Corntab" and "at" but not able to schedule.

I use putty for Unix.

Thanks
Vinit Raj

---------- Post updated at 06:04 AM ---------- Previous update was at 06:02 AM ----------

Hi,

Could you please help me out in scheduling a mail through Unix command.
I am using "Corntab" and "at" but not able to schedule.

I use putty for Unix.

presently i am using this command

Code:

echo "Test Mail through scheduling for 0553" | mailx -s "Check 123" xyz@abc.com | at 0553 Jan 6

Thanks
Vinit Raj

Moderator's Comments:

Please do not hijack a discussion concerning a different issue. If you want help with this problem, please repost this question in a new thread. Please also use CODE tags when sample code, sample input, or sample output.