Subject: suspend

From: "Jacqueline D. Hamilton" <[email-masked]>
Date: Wed, 11 Aug 1993 06:30:08 -0700

Does a verb that is suspend()'ed get killed when the server is
shutdown?  If not, isn't this sorta a security hazard?  After
all, what if someone writes a little verb,

  while (1)
    me.prop = 1;   # or some such.  something small that you wouldnt notice.
    suspend(0);
  endwhile

And sets it off, (or something similar)... there's no way to tell it's
running, like you can with forked tasks?  And so you could just go off
and forget you ever wrote it, while meanwhile the thing zooms away 
forever and ever?  Does this sorta thing cause problems?

-j.

---

From: Pavel Curtis <[email-masked]>
Date: Wed, 11 Aug 1993 11:01:03 -0700

> Date:	Wed, 11 Aug 1993 06:30:08 -0700
> From:	"Jacqueline D. Hamilton" <[email-masked]>
> 

Suspended (and read()ing) tasks are, indeed, maintained across server restarts,
just like forked tasks.  The only state lost across reboots is the actual
network connections, any unflushable output on those connections, and any
queued up lines of input from those connections.

The queued_tasks() built-in function includes in its returned value all forked,
suspended, and read()ing tasks in the queue, and the (historically-named)
`@forked' command shows that list, including the suspended tasks.

	Pavel