On 2004.06.08, Nathaniel H <[EMAIL PROTECTED]> wrote:
> AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem.  On 4.0.0 I
> can run both:
>
> 1. [exec /bin/bash -c "ls -al"]
> 2. [exec /bin/bash -c "/opt/myscript"]
>
> But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error.
>
> error waiting for process to exit: child process lost (is SIGCHLD ignored
> or trapped?)
>     while executing
>
> You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2
> on the problem 4.0.1 version.

This sounds exactly like the problem that Barry Books reported earlier
on this list about nsora and exec.  The newer Oracle client library
apparently either installs its own SIGCHLD signal handler, or throws
SIGCHLD itself.  This interferes with Tcl's SIGCHLD handler, therefore
when Tcl's [exec] executes something, it wants to be able to catch the
SIGCHLD of the child process when it dies.  Unfortunately, the signal
gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains
about it.

I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler
replacing Tcl's handler.

I don't know enough about nsjk2 or the various JVMs to know the answer
to this.

-- Dossy

--
Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of 
your email blank.

Reply via email to