Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Johnny B. Goode" <menotreadthis AT hotmail DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
X-Originating-Email:	[menotreadthis AT hotmail DOT com]
X-Sender:	menotreadthis AT hotmail DOT com
Message-ID:	<60E7170809C4FC4E825DDF39B7ECDE743B1B6C@hotmail.com>
References:	<20050609081844 DOT GE11065 AT calimero DOT vinschen DOT de>
Subject:	Re: Re: Error piping data through a cygwin command using rsh (write system call fail)
Date:	Fri, 10 Jun 2005 11:06:20 +0200

On Thu, 9 Jun 2005 10:18:44, Corinna Vinschen wrote:

> Did you try gzip -c ?

Hi Corinna.

I've just tried adding the -c option; it does not change anything. Actually,
I believe the -c option is default for gzip when no filenames are given as
parameters.

Also, the data leaves gzip without problems when piped through the pipeline
program, and the pipeline program then gets the error instead, which
indicates to me, that the error is not in the gzip program. It must be in
the system code behind the write call (since write actually returns a return
value that is not legal compared to the write call man page).

-- Soeren Hansen


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -