Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <3E3057F8.8071EAC1@wapme-systems.de>
Date: Thu, 23 Jan 2003 22:00:40 +0100
From: Stipe Tolj <tolj@wapme-systems.de>
Organization: Wapme Systems AG
X-Accept-Language: de
MIME-Version: 1.0
To: kouno_tetsu@artiza.co.jp
CC: cygwin@cygwin.com
Subject: Re: Apache corrupt big file
References: <GEEHDGCXV2VZWIH614XCLZYHD9PK.3e300606@067kohno2>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Tetsu KOUNO wrote:
> 
> I tried FTP(cygwin inetutils) download for the same file, it was successful.
> I think it means Cygwin APIs are okay even with my environment.
> It seems Apache specific issue...
> Any updates on this issue?

no, but that's not an adequate statement.

I know that FTP (and even SSH's scp) work. Apache does a lot more
thatn FTP or SSH, terms of socket connection pool re-use etc. So this
result is not an implication to your direction.

But why does the *same* Apache code run on 1.3.10-2 without any
problems?!

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

