Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: "D. N. Knisely" <dnk AT lucent DOT com>
To: <cygwin AT cygwin DOT com>
Subject: cygwin-1.3.11-3 Problem with Privoxy
Date: Mon, 24 Jun 2002 14:10:01 -0500
Message-ID: <LOEFIDOJKFHHHOOHLIHJAEGACGAA.dnk@lucent.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

I installed the new cygwin-1.3.11-3 libraries today.  I have been running an
OOTB build of privoxy (version 2.9.14), and it suddenly stopped working.
The error indicates that it can't fork with no error code (?) (it appears to
spawn a process when a new proxy access occurs).  At this point, I have not
looked further into the source code to see what is happening.  After
reverting to 1.3.10, it works just fine again.

Pending looking further into the code, are there any known issues with
forking with 1.3.11?  I have not noticed anything similar to this in the
discussion group yet.

Doug Knisely


--
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/