X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8BB82.27330280@onstor-exch02.onstor.net>; Wed, 21 May 2008 13:35:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: socat error
Date: Wed, 21 May 2008 13:35:05 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09624B14@onstor-exch02.onstor.net>
In-Reply-To: <20080521132307.3bfcb1ce@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: socat error
Thread-Index: Aci7gHtTV3QyJ2SuTnSB1o8yebx+kAAAW06w
From: "Rendell Fong" <rendell.fong@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>

Yes, I'm running with top of tree from dev branch.
I did a system upgrade so I wasn't sure whether certain files aren't
updated.


-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, May 21, 2008 1:23 PM
To: Rendell Fong
Cc: Larry Scheer
Subject: Re: socat error

On Wed, 21 May 2008 12:36:30 -0700 "Rendell Fong"
<rendell.fong@onstor.com> wrote:

> Are any of you seeing this error in console during initialization?=20
>=20
> 2008/05/21 12:13:26 socat[1161] E unknown option "-T60"; use option
> "-h" for help
>=20
> It looks the version of socat being used is from /usr/bin which
> doesn't have a -T option instead of socat from /onstor/bin which does
> have a -T option.  It's probably being invoked by support.sh and this
> option was added recently in change #29223.
>=20
> Sorry to ask if its already been resolved.
>=20
> Rendell=20

Hmm, this looks like something I might have accidentally broke, let me
take a look at it.  Is it on dev branch only, I hope?
