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 From: "Dave Korn" To: Subject: RE: Latest snapshot with XP SP2 and unison and cvs Date: Thu, 23 Sep 2004 10:44:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 23 Sep 2004 09:47:33.0486 (UTC) FILETIME=[598A90E0:01C4A152] > -----Original Message----- > From: cygwin-owner On Behalf Of Karl M > Sent: 22 September 2004 19:36 > Hi Dave... > > Sorry, I thought I covered all details, but... > > The firewall is off...I am behind a real firewall. > > The hanging can be averted by not using XP SP2 or by using a down rev > cygwin1.dll > > Thanks, > > ...Karl Yep, Corinna made that clear. Perhaps it's caused by SP2 putting tighter default ACLs on pipes than earlier versions did? There are various tools that can let you examine ACLs on devices and other objects, for instance ProcExp from sysinternals (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml). It might be informative to compare the ACLs on the pipe on a hung session with the ACLs on the pipe on a working session. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/