Subject: $scheduler v3.00

From: [email-masked] (Jonathan Bradshaw)
Date: Wed, 27 Oct 1993 23:54:54 -0700

I have a problem with the scheduler. When a number of insert and deletes
are performed by various forked tasks I get MANY :atrun() processes running
that do not die.

This seems to be because the scheduler is forking too many times. 

I think this must be to do with having 5 or 10 requests for scheduling
changes coming in off of 5 or 10 forked tasks!

I need idea on how to fix this problem.

-- 
 Jonathan Bradshaw | Preferred E-Mail is: [email-masked] | Ham N9OXE
 WNDU-AM/FM/TV South Bend IN | Opinions stated are mine and not of my employer
 PGP 2.2 Key fingerprint is:  EA 16 1B 5D 5D 94 6B 06  58 FD E6 E9 52 F3 6E 11
 "If any girl rejects you, don't you doubt it's part of the .plan" - D. Gibson

---

From: [email-masked] (Jonathan Bradshaw)
Date: Fri, 29 Oct 1993 13:08:35 -0700

> This might be a bug I let slip into the release. 
> Sorry about it, and I'll get back to you. 

The problem was solved using a fork() task that was killed and
rescheduled, but the ideal solution is still to use the scheduler. It may
be a server problem... something to do with the task being run multiple
times before the lock can be set. I've got this problem with a :notify
verb that sets a property so supposedly a routine only executes once no
matter how many times :notify is called. It doesn't work, the routine
gets called sometimes 3 times before the variable seems to lock it out.