This is a multi-part message in MIME format.
--------------090401040002030300060604
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi Wayne,
Thanks for the tip, however it wasn't so successful with my machine. The
errors still appeared, probably because its coming out of STDERR. I
tried redirecting STDERR and using the same method, but for some reason
STDERR won't be parsed by tail +2, its either all there or nothing.
Anybody else having luck/no luck?
Thanks,
Chris
--------------090401040002030300060604
Content-Type: message/rfc822;
name="Re: [Veritas-bu] Any Redhat 9 workarounds?"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="Re: [Veritas-bu] Any Redhat 9 workarounds?"
Return-Path: <WTSmith AT maine DOT edu>
Received: from frankfurt.ucdavis.edu (frankfurt.ucdavis.edu [169.237.104.161])
by pop11.ucdavis.edu (8.12.9/8.12.9/it-std-5.0.2) with ESMTP id
h9KFNITj019837
for <cjpelton AT green.ucdavis DOT edu>; Mon, 20 Oct 2003 08:23:18
-0700 (PDT)
Received: from samuel.unet.maine.edu (samuel.unet.maine.edu [130.111.39.86])
by frankfurt.ucdavis.edu (8.12.9/8.12.9/it-defang-5.1.2) with ESMTP id
h9KFNF6e008801
for <cjpelton AT ucdavis DOT edu>; Mon, 20 Oct 2003 08:23:15 -0700 (PDT)
Received: from osgood.unet.maine.edu (osgood.unet.maine.edu [130.111.39.64])
by samuel.unet.maine.edu (8.12.8/8.12.8) with ESMTP id h9KFLvmi019946;
Mon, 20 Oct 2003 11:22:20 -0400
Received: from maine.edu (wts.unet.maine.edu [130.111.39.47])
by osgood.unet.maine.edu (8.11.6/8.11.6) with ESMTP id h9KFM9d31930;
Mon, 20 Oct 2003 11:22:09 -0400
Message-ID: <3F93FDA0.6090707 AT maine DOT edu>
Date: Mon, 20 Oct 2003 11:22:08 -0400
From: Wayne T Smith <WTSmith AT maine DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4)
Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Chris Pelton <cjpelton AT ucdavis DOT edu>,
Veritas Netbackup mailing list <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: Re: [Veritas-bu] Any Redhat 9 workarounds?
References: <3F905F56.3090800 AT ucdavis DOT edu>
In-Reply-To: <3F905F56.3090800 AT ucdavis DOT edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean, Found to be clean
X-MailScanner-Information: Please contact the ISP for more information
X-Scanned-By: MIMEDefang 2.36
Chris Pelton wrote, in part:
> If anybody else has RH 9 working I would love to hear how.
Until Veritas corrects their problem, we've had good luck with the
following (reported on this list a couple of weeks ago) ...
The following workaround appears to work for us. We do NOT suggest it
will work for you, but since Veritas has, in our opinion, dropped the
Netbackup support ball on our RH foot, perhaps it is of some interest...
cheers, wayne
Netbackup v4.5 vs. RH9
The problem:
Because of some library issues when some Netbackup 4.5 executables
are run in RH9, a message is produced on stdout. The Netbackup server
doesn't tolerate this message and the backup or restore process is
terminated. The message is: Incorrectly built binary which accesses
errno, h_errno or _res directly. Needs to be fixed.
The workaround:
It appears to be sufficient to strip this message out. Netbackup
processing continues.
The details:
*
cd /usr/openv/netbackup/bin; mkdir rh9fix
*
mv bpbackup bpbkar bpcd bpclimagelist bplist rh9fix
*
create an executable named rh9fix.sh as:
#! /bin/bash
# Wrapper script to get rid of message:
#Incorrectly built binary which accesses errno, h_errno or _res
directly. Needs to be fixed.
#
# Message throws netbackup server off...
progname=$(basename $0)
/usr/openv/netbackup/bin/rh9fix/$progname | tail +2
*
create links for moved executables as follows:
ln -s rh9fix.sh bpbackup
ln -s rh9fix.sh bpbkar
ln -s rh9fix.sh bpcd
ln -s rh9fix.sh bpclimagelist
ln -s rh9fix.sh bplist
--
cheers, wayne
--------------090401040002030300060604--
|
