At 07:43 AM 5/8/2001 -0700, Larry Wall wrote:
>Dan Sugalski writes:
>: We'd want an alternative opcode running loop for all this, and it could
>: easily enough check times, as could special opcodes. Long-running codes
>: could also check at reasonable breakpoints. (Still in trouble with C
>: extensions, but that's pretty much a guarantee)
>
>It's not necessarily an alternative run loop--we need to do something
>like this anyway for safe signals. What's alternative is that the
>sandbox gets a periodic mandatory signal telling it to check resource
>limits.
Yeah, but the granularity for safe signals might be too coarse for good
resource management. Though we might not want to worry about quite that
level of granularity for sandboxes.
Brings to mind some of the issues with interrupting timers (alarm for
blocking I/O and such), unfortunately.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
