Minor problems with ELM and A/UX

[Kevin Rudd]

In article <23930 at memqa.uucp> qfhca81 at memqa.uucp (Henry Melton) writes:
>> 
>> Just as a wild guess, perhaps ELM is getting confused about signal handling
>> because of the SysV semantics being enabled by default.  Try sticking a 
>> call to set42sig() somewhere in the main() function and see if that helps.
>> I've found that's helped other programs that die strangely of "Alarm Clock",
>> and other programs as well -- as I recall, Epoch didn't work worth a damn
>> until I put the set42sig() in...
>> --
>> Richard Todd	rmtodd at uokmax.ecn.uoknor.edu  rmtodd at chinet.chi.il.us
>> 	rmtodd at servalan.uucp
>> "Elvis has left Bettendorf!"
>
>Great info!  set42sig let me compile oneko.  Keep these tips coming.
>
>
>
>-- 
>Henry Melton  qfhca81 at memrqa.sps.mot.com 
>{slow}  qfhca81 at memqa   ..!cs.utexas.edu!execu!sequoia!memqa!qfhca81
>{home}  henry at hutto     ..!emx.utexas.edu!hutto!henry

I was having the same problem and excitedly inserted set42sig() into my
elm main() function as the first statement and rebuilt elm.  Unfortunately,
after a while I received an "Alarm Clock" return to the shell as always.

Either there is something else going on or I put this in slightly wrong...

  -- Kevin

--
questions, comments, free two page monitors, contact kevin at trump.Stanford.EDU
complaints, bills, other crises, contact guido at outback.Mob.COM