Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site baylor.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!rochester!rocksvax!rocksanne!sunybcs!kitty!baylor!peter From: peter@baylor.UUCP (Peter da Silva) Newsgroups: net.unix Subject: Re: alarms and longjmp Message-ID: <356@baylor.UUCP> Date: Mon, 12-Aug-85 11:38:39 EDT Article-I.D.: baylor.356 Posted: Mon Aug 12 11:38:39 1985 Date-Received: Thu, 15-Aug-85 00:11:34 EDT References: <666@cybvax0.UUCP> Distribution: net Organization: Ancient Illuminated Seers of Bavaria Lines: 17 > What is the proper behavior of an alarm call. > > Below is an extract of a public domain program. > To get it to work on a VAX (4.2) I made some changes. > What is the proper way to handle the timeout condition ? > Is the original way "legal" (I know it works on most machines) ? The original way worked on everything except a 4.2 system. UCB wanted a cleaner way to deal with signals that didn't trash system calls, so they changed the way they worked. The fact that they didn't leave the old method in is my only major gripe with 4.2. They should have at least implemented a "killsys()" call when you wanted to abort the system call you happened to be in when the alarm occurred. -- Peter da Silva (the mad Australian) UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter MCI: PDASILVA; CIS: 70216,1076