X-Spam-Check-By: sourceware.org X-BigFish: V Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Perl failure Date: Wed, 12 Jul 2006 17:08:43 -0700 Message-ID: From: "Bruce Dobrin" To: X-IsSubscribed: yes 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k6D0AB8p032476 Hi, I have a server that has been doing back end maintenance using perl on cygwin for 6 years now. I recently upgraded from win2k and cyg1.5.9 to XP sp3 and cyg1.5.19 (to be fare, I also cleaned up the perl code a bit). The script checks versioning and build info on about 600+ windows systems. Since the upgrade, it gets thru about 500 of them ( almost exactly 2 hours) and then: panic: MUTEX_LOCK (45) [util.c:2266] at /c/dist_and_install_files/source/dist2/spUpdate2d.pl line 24, line 277. panic: MUTEX_LOCK (45) [op.c:354], line 277. It hits a slightly different time and position in the list each time, but always after approximately 2 hours. I found a few old mails suggesting rebaseall, which I ran to no effect. The system pretty much runs nothing but this. I've been running a version of this script since cyg1.3.9 and never had a problem like this one. Any suggestions? Thanks Bruce D -- 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/