Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3E3D108F.226AEDC7@wapme-systems.de> Date: Sun, 02 Feb 2003 13:35:27 +0100 From: Stipe Tolj Organization: Wapme Systems AG X-Accept-Language: de MIME-Version: 1.0 To: kouno_tetsu AT artiza DOT co DOT jp CC: cygwin AT cygwin DOT com Subject: Re: Apache corrupt big file References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Tetsu KOUNO wrote: > > (6) ServerType > ServerType inetd ... successful!! > Maybe, same reason to ftp download was successful. > > Any idea? the inetd variant, means that on every incoming TCP connect on port 80 (or whatever you have confiured), inetd will spawn an httpd prozess for that specific connection. This is less TCP connection fault tolerant, yes. The problem within the current Apache+Cygwin (normal setup) is within the accept() serialization, which means the mechanism that the core parent httpd prozess deals with incoming TCP connect and spreads the load across the idle child httpd within the scoreboard file. Unfortunatly it's unclear to me why the beast serves for a couple of requests and then suddenly stops doing this. Stipe tolj AT wapme-systems DOT de ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: info AT wapme-systems DOT 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/