On Sep 6, 2008, at 11:57 PM, Craig A. Berry wrote:
On Sat, Sep 6, 2008 at 5:58 PM, John E. Malmberg <[EMAIL PROTECTED]>
wrote:
We need to have a method of killing the Perl process with out
killing the
shell on VMS.
What I ended up doing is making it send a SIGTERM rather than SIGKILL
On Sep 6, 2008, at 8:42 PM, Fred Morris wrote:
As I recall the FORCEX system service also takes an optional status
code to be
used by the exiting subprocess... don't know if that helps or not.
On Saturday 06 September 2008 15:33, Hein van den Heuvel wrote:
You may want to check out SYS$FORCE
As I recall the FORCEX system service also takes an optional status code to be
used by the exiting subprocess... don't know if that helps or not.
On Saturday 06 September 2008 15:33, Hein van den Heuvel wrote:
> You may want to check out SYS$FORCEX
> That would kill an (perl) image but leave DCL
You may want to check out SYS$FORCEX
That would kill an (perl) image but leave DCL (command file) running.
In more recent OpenVMS version this is also availabel as DCL command
STOP/IMAGE. The system service has always been there.
fwiw,
Hein.
On Sat, Sep 6, 2008 at 5:58 PM, John E. Malmberg <[
Craig A. Berry wrote:
Given the rate of Nicholas's integrations, this is now somewhat old
news, but here's where things were as of sometime last night with a
-Dusethreads build on OpenVMS Alpha v8.3:
ext/threads/t/free2.FAILED--expected 78 tests,
saw 65
ext/threads/t/f
Given the rate of Nicholas's integrations, this is now somewhat old
news, but here's where things were as of sometime last night with a -
Dusethreads build on OpenVMS Alpha v8.3:
ext/threads/t/free2.FAILED--expected 78 tests,
saw 65
ext/threads/t/free.
