Path: utzoo!attcan!uunet!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!mcdchg!ddsw1!proxima!lucio
From: lucio@proxima.UUCP (Lucio de Re)
Newsgroups: comp.os.minix
Subject: Re: PH 1.5 problems
Message-ID: <2137@proxima.UUCP>
Date: 24 Jan 91 07:35:01 GMT
References: <7105@crash.cts.com>
Organization: FLAGSHIP Wide Area Networks - Cape Town
Lines: 23

In article <7105@crash.cts.com> cwr@pnet01.cts.com (Will Rose) writes:
>king@hpfcdj.HP.COM (Mike King) writes:
>>Other problems I have found with the stock Prentice Hall 1.5,
>>which is equivalent to 1.5.10, release are:
> 
>>1.  The alarm clock goes off when using VI, forcing you to
>>    logoff and then log back in and virecover the file.
> 
>The only placed with the string "Alarm" anywhere in the 1.5.10 system
>is the shell; presumably it's catching a SIGALRM, or thinks it is.
>Does it have enough stack?

Does it matter? Considering that Elvis fails at that point, presumably
a SIGALRM does originate somewhere, and although the shell catches it,
Elvis defaults to standard behaviour (terminate, without even resetting
cooked mode). So my diagnosis is that a SIGALRM does originate (valid
or invalid) somewhere, the question is: Where?

--
Lucio de Re.

internet: lucio%proxima@ddsw1.mcs.com
uucp:   ...!uunet!ddsw1!proxima!lucio