What about running a separate program that does the timing, and then at the
specific time sends a message to the running process?  The external program
(i.e., timer program) could even kill the process from without. Just a
thought

-----Original Message-----
From: Robert Glaubius
To: <cs.berkeley.edu at allegro-cl>
Sent: 3/8/02 3:23 PM
Subject: counting time

Hi,

If any of you could help me out with this, it'd be greatly appreciated.
I've got a project that I want to cut CPU time for processing at 1 hour,
after which I want to record results before halting the program.  I'm
using ACL 6.1.  Previously I've used (get-internal-run-time) to grab the
initial point, and then checked to see if the new
(get-internal-run-time)
minus the old was greater than 1 hour, but the concern is whether or not
the time counted will include time sharing, and therefore be dependent
on system load.  If anyone has some insight into this, please, let me
know.

Thanks,

Rob Glaubius