Path: utzoo!utgpu!watmath!clyde!att!rutgers!mit-eddie!uw-beaver!ssc-vax!uvicctr!tholm
From: tholm@uvicctr.UUCP (Terrence W. Holm)
Newsgroups: comp.os.minix
Subject: Re: Bug in lib/system.c  - New deadlocks in PC Minix
Message-ID: <568@uvicctr.UUCP>
Date: 5 Dec 88 20:50:18 GMT
References: <753@faui10.informatik.uni-erlangen.de>
Reply-To: tholm@uvicctr.UUCP (Terrence W. Holm)
Organization: University of Victoria, Victoria B.C. Canada
Lines: 29

In article <753@faui10.informatik.uni-erlangen.de> rtregn@faui44.informatik.uni-erlangen.de (Robert Regn) writes:
>
>I have detected a bug in lib/system.c (V1.3b == latest)
>A failing fork exits the entire process - very bad for editors
>with modified buffers !


A patch was already posted as EFTH MINIX report #52 in October.
That patch also disabled sigint/sigquit in the parent.
Note that MINIX-ST users must use execl( ..., (char *) 0 ).



>I'am working with Minix very often connected with tty1
>(remote login from a Sun ).
>If two or more processes write simultaneously on tty1, one of them hangs
>on FS. Trying to kill it hangs the system.
>


Yes, the problem has been around for awhile. It is a real pain in
the axx. I have been trying to get some non-MINIX work done, so
haven't looked at it for a few weeks.


			Terrence W. Holm
			  uunet!uw-beaver!uvicctr!tholm
			  tholm%uvunix.bitnet
			  tholm%sirius.UVic.ca@relay.ubc.ca