Re: Problems with syscall <async>

   From: "Trever L. Adams" <[email protected]>

   The first three are the crm file (web_categorize.crm) and the stdout, 
   stderr. There are 997 other open files. These are all pipes. Does crm114 
   not look to and free the pips in syscall <async>? Is there a way to do 
   it? Nothing needs to be fetched from the child process (as it is 
   provided with the file as input and is told to hand the response back in 
   a named pipe/fifo . I don't think <keep> fits.

   Are there any solutions?

Whoa!!!  BIG BUG, and you found it.

I'd been looking for that one for quite a while myself, and
was making no progress.  This is probably the same bug that
is causing what seems like a hang on tenfold_validate.crm when
run with the FSCM classifier - the failure to close pipes.

Thanks!

As an interim workaround, launch a bunch of single-pass 
learn / classifies from bash.  That will keep you going till
we squash this bug.

(and here I was, fixing a little syntax gotcha in "isolate" and
"syscall".  The issue was that
  
  syscall / \/etc\/usr\/local\/bin\/blah/

is highly error prone; the callee isn't even really a pattern, so 
the new version allows boxes as well as slashes for the thing to run:

  syscall [ /etc/usr/local/bin/blah ] ( :my_input: ) ( :my_output:)

This will be up soonish; the old format with slashes is still allowed.

     - Bill Yerazunis

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/