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
Date: Mon, 24 Jun 2002 21:25:39 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-1.3.11-3 Problem with Privoxy
Message-ID: <20020625012539.GI32490@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <LOEFIDOJKFHHHOOHLIHJAEGACGAA DOT dnk AT lucent DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <LOEFIDOJKFHHHOOHLIHJAEGACGAA.dnk@lucent.com>
User-Agent: Mutt/1.3.23.1i

On Mon, Jun 24, 2002 at 02:10:01PM -0500, D. N. Knisely wrote:
>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).

Sounds a lot like the dreaded "two versions of cygwin1.dll on your system"
problem.

cgf

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