Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site cyb-eng.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!ut-sally!cyb-eng!howard
From: howard@cyb-eng.UUCP (Howard Johnson)
Newsgroups: net.unix-wizards
Subject: Re: fork timing hole? (nope)
Message-ID: <671@cyb-eng.UUCP>
Date: Fri, 16-Aug-85 03:10:38 EDT
Article-I.D.: cyb-eng.671
Posted: Fri Aug 16 03:10:38 1985
Date-Received: Mon, 19-Aug-85 20:50:53 EDT
References: <541@unisoft.UUCP>
Distribution: net
Organization: Cyb Systems, Austin, TX
Lines: 41

Explanation:  If you look closely at the sh/csh code, you'll find cases
where sh and/or csh catch SIGINT and emit a newline.  Specifically, it's
the parent shell which does this if it's interrupted while waiting for
the child to terminate.  By the way, receipt of the interrupt character
generates a SIGINT for every process in the controlling terminal's
process group.

> The Scenario:
> 	"ls<ret><del>"
> What happens? 1 of 3 things
> 
> 1) 
> 
> $ ls
> 
> $
> 
> 2)
> 
> $ ls
> $
> 
> 3)
> 
> $ ls
> my
> local
> files
> $

>	... [wild speculation]

> Finally, my question ..... Is this a bug??
> 		Paul Campbell
> 		..!ucbvax!unisoft!paul

In the shell, yes; in the kernel, no.  (Just a little tip from
one of your customers, Paul.)
-- 
..!{seismo,topaz,mordor,harvard,gatech,nbires,ihnp4}!ut-sally!cyb-eng!howard
(ordered best to worst); also ..!{ut-ngp,shell}!cyb-eng!howard  +1 512 458 6609