Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!nic.MR.NET!umn-cs!brsmith
From: brsmith@umn-cs.CS.UMN.EDU (Brian R. Smith)
Newsgroups: comp.windows.x
Subject: Re: "Alarm clock" from Xfig
Message-ID: <15877@umn-cs.CS.UMN.EDU>
Date: 13 Sep 89 20:30:06 GMT
References: <258@enuxha.eas.asu.edu>
Organization: University of Minnesota, Minneapolis
Lines: 20

rao@enuxha.eas.asu.edu (Arun Rao) writes:
>	I saw a posting last week (or earlier ?) about someone who
>	kept getting an "Alarm Clock" message while entering text
>	into Xfig on his Mips machine.

>	Did anyone post a fix for this bug ? We have exactly the
>	same problem with our Ardent Titan. The funny thing is
>	that the message persists even after Xfig has aborted -
>	even the 'ls' command will yield "Alarm clock" a few
>	times.

>	What *does* the message mean, anyway ?

It's printed by csh when one of its children (commands) dies from
the SIGALRM signal.

That's probably not helpful, but it is intriguing...  maybe you've
got a homicidal process hanging around.

Brian