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: "D. N. Knisely" To: Subject: RE: UW imapd and cygwin1.dll 1.3.13-2 Date: Thu, 14 Nov 2002 16:54:43 -0600 Message-ID: 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.2800.1106 As I responded earlier, the 1.3.13 snapshot did fix the problem with UW imapd. However, all actual releases of the cygwin1.dll since that time have result in the same broken behavior (hangs waiting in a poll waiting for some signal). I tried all intermediate versions up to 1.3.15-2 with no luck. At this point, I am stuck back at 1.3.12. Is there anything different between the fix in the snapshot after 1.3.13-2 vs. the actual releases later? Any suggestion on what I might try? By the way, for other imapd users, this problem only occurs when used with Microsoft's Outlook IMAP implementation; other IMAP clients work OK, so it is something unique to the way Outlook uses IMAP services. D. Knisely >>It looks like something has changed in 1.3.13-2 related to poll or waiting >>for signals? Possibly there has always been a race condition that is now >>occurring 100% of the time with 1.3.13-2, but never occurred with previous >>versions. >> >>Has anything changed related to polling/waiting for signals in 1.3.13? >Check other threads in the cygwin mailing list. This is always a good plan >when you have a problem. >If you had done so, you would have noticed other people reporting >similar problems and me suggesting that they run the latest snapshot. -- 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/