hello, Isn't there another consideration? MacPerl is not threaded, so even if the process is "polite", it will tie up MacPerl while it is running. I think to have more than one MacPerl process, you need to have MacPerl running with a different creator code. I think Chris Nandor wrote a MacPerl cron script a while back ... it might be instructive to see what strategy he used to get around this limitation. on 1/26/00 5:08 AM, Brian McNett at webmaster@mycoinfo.com wrote: > > The easy stuff is done. Next comes the hard part: Making the process > "polite" so that it gives it's clock cycles back to the OS. > > Brian McNett, Webmaster -- Enrique Terrazas, MD <mailto:terrazas@labmed.ucsf.edu> <http://pangloss.ucsf.edu/~terrazas/> # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org