Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com List-Unsubscribe: List-Archive: List-Help: , Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <19990806232455.20042.rocketmail@web129.yahoomail.com> Date: Fri, 6 Aug 1999 16:24:55 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: 19990805 Snapshot!! To: cygwin developers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii It seems that the bugs are back with [no]ntsec. I'll try to send Corinna a strace. Those of you who are having problems with GET_SIGNAL_MUTEX errors spitting on the screen try CYGWIN=nontsec to see if it helps. Corinna's code shouldn't have an affect on Win95 but who knows. Corinna, if you have Win9x and you also have created an /etc/passwd and /etc/group files will the ntsec code cause problems? Further notes on the ntsec problem, in starting a second bash, I'm no longer the owner of the child process ( or so it appears ). I can't kill it with the cygwin kill ( because I'm not the owner ) or with the NT TASK MANAGER ( because I don't have the privileges ). If I kill the parent process, which I can do only from TASK MANAGER the parent CMD process will disappear along with the parent bash process but the bash child process remains along with the GUI which is in limbo doing nothing. The only way to get rid of these is to go to the Application tab of the TASK MANAGER and kill the application. NT4 sp3 Normal domain user. I have no /etc/passwd and no /etc/group files. CYGWIN=notty binmode notitle. Hope this helps, === Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) _____________________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com