topic Re: fbackup returncode with a pipe in Operating System - HP-UX

fbackup returncode with a pipe

Wessel Baptist — Thu, 14 Jun 2001 08:15:48 GMT

When I submit "commandA pipe commandB" are there any possibilities to see the returncode of commandA?
What am I doing?
fbackup -v | tee logfile
After completion of fbackup I want to know the returncode of fbackup.

Thanks so far.
Wessel

Re: fbackup returncode with a pipe

Stefan Farrelly — Thu, 14 Jun 2001 08:31:10 GMT

Instead of doing fbackup | tee
you can do;

#!/bin/sh
exec 1> 2>&1
fbackup ....
echo $?

Now you can still get full log output to logfile and still pick up and process the return code from fbackup.

Re: fbackup returncode with a pipe

federico_3 — Thu, 14 Jun 2001 08:50:19 GMT

echo $?
I'll do a script like this:

exec 1 > /tmp/logfile 2>&1
fbackup ....................
echo $?

Re: fbackup returncode with a pipe

Wessel Baptist — Thu, 14 Jun 2001 10:42:32 GMT

Hi,

this is not what I'm looking for.
I like to the output of fbackup on screen, so I can see the progress of fbackup, therefore I use -v switch and at the same time I want to log every fbackup-message.
And after fbackup has finished I want to test the returncode of fbackup.
If returncode is not equal to zero I want to look in the logfile for "serious" messages.

Re: fbackup returncode with a pipe

James R. Ferguson — Thu, 14 Jun 2001 11:03:01 GMT

Hi Wessel:

You CAN achieve exactly what you are seeking by using the scheme below. For simplicity, I have placed elipses ("...") in place of the options to 'fbackup':

# ( fbackup ... 2>&1 ; echo $? > /tmp/fb.xit ) | tee -ia /tmp/fb.log

# EXITV=`< /tmp/fb.xit`

# if [ $EXITV -eq 0 ]...

...JRF...

Re: fbackup returncode with a pipe

Wessel Baptist — Thu, 14 Jun 2001 13:19:51 GMT

Hi James,

the "tee" in the 1st line, "tee's" only the results of the "echo $? > file". So the result of "tee -ia file" is an emty file.
Do you have any alternatives.

Thanks, Wessel

Re: fbackup returncode with a pipe

James R. Ferguson — Thu, 14 Jun 2001 14:03:13 GMT

Hi Wessel:

Sorry, I lifted some of my code out of context. Try this:

# ( fbackup ... 2>&1 ; echo $? > /tmp/fb.xit ) | tee -ia /tmp/fb.log

# EXITV=`cat /tmp/fb.xit`

# if [ $EXITV -eq 0 ]...

...JRF...

Re: fbackup returncode with a pipe

Vincent Stedema — Fri, 15 Jun 2001 08:42:26 GMT

Hi Wessel,

Here's some sample perl code that can be used to send output from within a script to multiple file handles:

#!/usr/bin/perl -w

# save the old file handle for STDERR
open(OLDERR, ">&STDERR");

# create some new ones to send output to
# screen and log file
open(OUTFILE, "| tee fbackup.log");
open(STDERR, ">&OUTFILE");
select(OUTFILE);

# send output to tee pipe
$result=system("fbackup ...");

# close output to tee pipe
close(STDERR);
close(OUTFILE);

# send output to STDOUT
select(STDOUT);
# re-attach STDERR
open(STDERR, ">&OLDERR");

if(!$result) {

... your code here ...
}

Hope this works :-)

Vincent

Re: fbackup returncode with a pipe

Wessel Baptist — Mon, 18 Jun 2001 12:46:57 GMT

Hi Vincent,

I found perl in /usr/contrib/bin and I've tried your script and this works. Now I have the same output on screen as wel as in a file. Thanks a lot.
B.t.w. where can I find information / manuals over perl. I don't know anything about perl.

Re: fbackup returncode with a pipe

Vincent Stedema — Mon, 18 Jun 2001 13:09:27 GMT

Hi,

The No. 1 resource is http://www.cpan.org

AFAIK, the perl version shipped with HP-UX 11.00 is 4.??, which is not as powerful as the more recent versions (5.*). You'll find a depot for a more recent version at http://hpux.tn.tudelft.nl/hppd/hpux/Languages/perl-5.6.1/ .

Regards,

Vincent

Re: fbackup returncode with a pipe

Wessel Baptist — Thu, 06 Sep 2001 13:33:30 GMT

I took another look and the solution of James R. Ferguson is exactly what I needed.
Thanks
Wessel

Re: fbackup returncode with a pipe

James R. Ferguson — Thu, 06 Sep 2001 13:39:15 GMT

Hi Wessel:

Thank you very much! And, thanks for taking the time to track this thread down to say so. You make it all worthwhile.

With my warmest regards, Jim.

...JRF...