building scheme48 without setitimer ?
Ian Horswill <ian <at> ils.nwu.edu>
1997-12-29 16:40:01 GMT
The simplest thing to do would be to write your own setiitimer
procedure. All setitimer does is schedule a periodic interrupt. It's
basically a better version of the old alarm system call that allows
you to choose between counting in real time and counting used CPU
time, to set a timer to go off at regular intervals, and use
scheduling intervals of less than a second.
-ian
>From dima <at> duti515a.twi.tudelft.nl Tue Dec 30 13:08:10 1997
Received: from duti515a.twi.tudelft.nl by martigny.ai.mit.edu with ESMTP
(1.40.112.8/16.2) id AA005875290; Tue, 30 Dec 1997 13:08:10 -0500
Return-Path: <dima <at> duti515a.twi.tudelft.nl>
Received: by duti515a.twi.tudelft.nl
id m0xn778-0004ShC
(Debian Smail-3.2 1996-Jul-4 #2); Tue, 30 Dec 1997 20:14:06 +0100 (CET)
Message-Id: <m0xn778-0004ShC <at> duti515a.twi.tudelft.nl>
Date: Tue, 30 Dec 1997 20:14:06 +0100 (CET)
From: Dmitrii Pasechnik <dima <at> duti515a.twi.tudelft.nl>
To: ian <at> ils.nwu.edu
Cc: dima <at> duti515a.twi.tudelft.nl, scheme48-bugs <at> martigny.ai.mit.edu
In-Reply-To: <199712291640.KAA32350 <at> ianpc.ils.nwu.edu> (message from Ian
Horswill on Mon, 29 Dec 1997 10:40:01 -0600)
Subject: Re: building scheme48 without setitimer ? tests, please?
Date: Mon, 29 Dec 1997 10:40:01 -0600
From: Ian Horswill <ian <at> ils.nwu.edu>
The simplest thing to do would be to write your own setiitimer
procedure. All setitimer does is schedule a periodic interrupt. It's
basically a better version of the old alarm system call that allows
(Continue reading)