Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site uokmet.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!okstate.UUCP!uokmet.UUCP!root
From: root@uokmet.UUCP
Newsgroups: net.bugs.2bsd
Subject: Re: init
Message-ID: <1500012@uokmet.UUCP>
Date: Thu, 9-Jan-86 11:09:00 EST
Article-I.D.: uokmet.1500012
Posted: Thu Jan  9 11:09:00 1986
Date-Received: Fri, 17-Jan-86 02:22:09 EST
References: <810@lsrhs.UUCP>
Lines: 27
Nf-ID: #R:lsrhs.UUCP:810:uokmet.UUCP:1500012:000:968
Nf-From: uokmet.UUCP!root    Jan  9 10:09:00 1986


>There is apparently a very interesting (and annoying) bug in 2.9's init, or
>so we have encountered.  If ^C is hit in between when init forks and when
>getty is exec'd, SIGINT is sent to init.  Sometimes this even happened to
>running login's.
>
>This bug should be able to be reproduced by repeatedly hitting ^C at any
>currently running getty or login.  The result of this is that init's child
>thinks it's going into special session.  It logs everyone out and is a
>rather nasty problem.  (A question: when this happens, it sometimes happens
>that not everyone is logged out.  Why would kill(-1, SIGKILL) not always
>work?)
>
>Our second solution was to signal(SIGINT, SIG_DFL), rather than setpgrp().

You should also add:
	signal(SIGQUIT, SIG_DFL);

Another way to produce the problems is to have root do a "kill -2" on *ANY*
init processes.

	Kevin W. Thomas
	Univ. of Oklahoma
	School of Meteorology
	Norman, OK

UUCP:	...!ihnp4!okstate!uokvax!uokmet!kwthomas