Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: andrew_lawrence AT uk DOT ibm DOT com X-Lotus-FromDomain: IBMGB To: cygwin AT sourceware DOT cygnus DOT com Message-ID: <80256922.00463962.00@d06mta09.portsmouth.uk.ibm.com> Date: Thu, 20 Jul 2000 13:45:34 +0100 Subject: Bash issue... IBM / Comet Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline To: psalazar AT redhat DOT com cc: ltomlinson AT cygnus DOT co DOT uk, icole AT redhat DOT com From: Andrew Lawrence1/UK/IBM AT IBMGB Subject: Bash issue... IBM / Comet Importance: Urgent Paul...hi I have left you a voice message...we have an urgent issue with an implementation of BASH 2.02 (I am advised by Sygnus at Cambridge that you have picked up my original Email with the detail?)...I am working with Comet (A high street Electrical retailer) on a store application that is due to rollout in mid August. We have completed 2 pilots but the stores have to be mandandled after crashing on a regular basis due to the issue we have highlighted as Bash centered. We are due to Pilot more stores next week, but need to make a decision today as to wether to move on. Trawling through the Cygnus bulletin boards we have found reference to the same problem...but the fix indicated does not resolve our set up. I have asked Redhat and Cygnus for some on site support... We are looking for any avenue of assistance and would appreciate if you can come back to me with some advice, or point me in the right direction...Our Tech specialists can enlarge on the problem further and explain what we have done to date. Attached are some notes from a review this morning...probrably won't mean a lot though! My contact numbers are attached, plus UK 01923 714815... (Redhat reference, by copy Ian, can you help at all following the attached note to me?) "WE are trying to find somebody in UK who can help - if not I will refer to Germany or US. Please bear with us, Once I understand nature of solution we can discuss commercial relationship. If it requires developer time we sell blocks of 40 hours that can be called off as required Ian") Many thanks for any assistance... A. ANDREW LAWRENCE ITS NW & DT Project Manager CONTACT INFO: 020 8380 (33)0462 / Mobile 07710 820751 / Mobx 276149 Fax: 020 8380 0527 Email: Andrew_Lawrence AT uk DOT ibm DOT com Address: IBM BRENTFORD, West Cross Centre, Great West Rd, Middx, TW8 9DE ---------------------- Forwarded by Andrew Lawrence1/UK/IBM on 07/20/2000 11:58 AM --------------------------- Andrew Lawrence1 07/20/2000 11:55 AM To: Peter DOT Lynch AT comet DOT co DOT uk, Zeiniz DOT Virani AT comet DOT co DOT uk, Jim DOT Parsons AT Comet DOT co DOT uk, Mark Canning/UK/IBM AT IBMGB, David Aydon/UK/IBM AT IBMGB, Kate DOT Woods AT comet DOT co DOT uk, dmurgatroyd AT progressive DOT uk DOT com, Nicholas E Lansdowne/UK/IBM AT IBMGB cc: Russell Vize/UK/IBM AT IBMGB From: Andrew Lawrence1/UK/IBM AT IBMGB Subject: Bash issue Review 20/07/00 Minutes from review...and update... summary: We are currently running bash 2.02 under Windows Nt 4.0 Service pack 5 and CYGWIN1.dll. We appear to have a problemwith bash commands hanging. Under further investigation we found that the internal bash "Process table" contained 60+ processes by using the "ps -al" command. This command lists both the "WINPIDS and Bash's own PID" and from looking at this list, they were only about 25 processes which were actual processes. If we issued the command "ps | wc -l" continuously then after about 3 iterations, the process would hang. This would have an knock on effect in that any processes that use any bash commands would just hang as well. When we killed the offending process,everything continued ok. The Cometnet environment with NT serv pack 6a appeared to not exhibit problem...Action: following meeting DA/JP managed to recreate too (it just takes longer to recreate the problem...but once exhibited it will not go away), so that avenue closed. Conflict is definately an environmental issue with the implementation of Bash / NT / Progressive... Action: DA / JP have put a base (plain vanilla) NT / Bash build together and problem still exists...Sygnus could therefore still recreate this too if necessary. (Screen sizing an issue within the main problem, ie on PC images the issue can only be recreated in a window, and not full screen. on Server issue is recreated in both window and full screen!) AL to keep talking to Sygnus...latest post meeting, A specialist according to Sygnus(Paul Salazar) is dealing with the issue, but is based in Sunnydale California. Phone Messages left for an update! Sygnus in Cambridge have been unable to reply to any of AL's questions, and have diverted issue to Paul Salazar. MS Dos settings (Progressive?) ZV raise issue post meeting that Progressive believe they may have another route of enquiry, MC to review... Re moving ahead the Pilots, we will need a kill shutdown process (for Bash, after it has shutdown Tivoli), written on C and tested. Resource and Time issue to implement. Help desk and early AM each day to activate is a support issue too. MC will look at shutdown flags and an easy way of implementing to avoid too much time writing a kill programme (was sourced [PSKILL from sys internals] post meeting by MC). This is a dirty solution, and the teams decision was that to move on with Pilots with this dirty reboot every day will cause more bad PR than good. Will pick up and PM team review this am... Rgds A. ANDREW LAWRENCE ITS NW & DT Project Manager CONTACT INFO: 020 8380 (33)0462 / Mobile 07710 820751 / Mobx 276149 Fax: 020 8380 0527 Email: Andrew_Lawrence AT uk DOT ibm DOT com Address: IBM BRENTFORD, West Cross Centre, Great West Rd, Middx, TW8 9DE -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com