This is the mail archive of the cygwin-developers@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

19990805 Snapshot!!


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 <mailto:earnie_boyd@yahoo.com>

Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>

(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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]