From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37985 invoked by alias); 30 Dec 2016 19:25:04 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 37951 invoked by uid 89); 30 Dec 2016 19:25:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 spammy=antivirus, worthy X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Dec 2016 19:25:02 +0000 Received: from [192.168.0.3] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id D9EF24018072; Fri, 30 Dec 2016 10:46:00 -0500 (EST) Reply-To: moss@cs.umass.edu Subject: Re: Cygwin 2.6.0 Fork issue References: To: cygwin@cygwin.com From: Eliot Moss Message-ID: <83a7f28d-3ad3-8f37-5a4c-2416d0121a0c@cs.umass.edu> Date: Fri, 30 Dec 2016 19:25:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-12/txt/msg00285.txt.bz2 Looking at what you sent I see at least two suspicious things: 1) SEVERAL orphaned Cygwin installations. This indicates you may have multiple installation of Cygwin in different places, and this can certainly lead to trouble. 2) A number of files missing from certain packages, which (at a glance) all seemed to be under /opt or /sbin. Did you happen to delete those hierarchies? Or is there some reason they could not be created? I am not quite as expert at figuring out this sort of problem as some others on the list, so I might be barking up the wrong tree, but these seem worthy of investigation. One way to fix things is to remove *all* Cygwin installations (see the installation mentioned in the cygcheck output) and reinstall Cygwin from scratch, paying attention if any files could not be created (the /opt and /sbin concern). There may be simpler fixes. And of course this does not rule out BLODA (badly behaving other programs that interfere with Cygwin's mechanisms - often anti-virus and similar tools). Regards - Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple