🚀 go-pugleaf

I am porting a simple signal-processing interpreter to NeXT.  Before I
give it an application interface I'm ironing out the bugs in the core
interpreter.  The interpreter itself compiles and runs under almost
any C compiler.  It uses popen(3) to create and manage subprocesses
for certain parts of its work.  Since the interpreter catches signals,
I preface the popen(3) call with calls to signal(3c) to ignore
SIGINT, etc. so that the child process is protected.  This works on
other systems I'm using, e.g. Ultrix.  Under NS 2.1 though, the
subprocess receives interrupts, and dies.  What have I overlooked?
I've read the manpages for popen(3), signal(3c), sh(1), and execve(2)
but haven't found any insights.  I wish my problem were more NeXTstep
than Unix, but I've got to start somewhere.

--
Hugh Secker-Walker                    INTERNET:  hugh@ear-ache.mit.edu
MIT, Research Lab of Electronics      UUCP:      mit-eddie!mit-athena!hugh
     "The good news is the ear has 30,000 channels to the brain,
      the bad news [sic] is they're all nonlinear" -- M.B. Sachs