For those of us who don't understand the low level nuts and bolts: It
doesn't seem practical to be able to trap EVERY error. Disabling ^C
might be OK for a 'production' system, but I need a way out from the
crashes I seem to produce pretty frequently (even if they are my fault-
which most probably are). How should we invoke ^ZU for a 'production'
system? Is this the 'auto-start mode'? And how does one do this?
Mike
Bhaskar, KS wrote:
Greg --
Again, this seems consistent with the semantics of the JOB command. I don't
see where killing a process with SIGKILL (9) drops you back to the direct mode.
To me, what is interesting is that killing the process owning the lock doesn't
allow the process waiting for the lock to eventually get the lock, and you have
to hit ^C. In GT.M, the process waiting for the lock eventually gets the lock,
as in the example below.
Here is session 1:
[EMAIL PROTECTED]:~/tmp/test$ cat zzloop.m
ZZLOOP L +^ZZZZ F S X=1 HANG 0.5
Q
[EMAIL PROTECTED]:~/tmp/test$ mumps -dir
GTM>J ^zzloop
GTM>L +^ZZZZ
<-- when process 6006 is killed, this process (6003)
eventually gets the lock without needing a ^C.
GTM>h
Here is session 2:
[EMAIL PROTECTED]:~/tmp/test$ ps -ef| grep mumps
bhaskar 6003 5985 0 06:56 pts/5 00:00:00 mumps -dir
bhaskar 6006 1 0 06:57 ? 00:00:00 /usr/local/gtm/mumps -direct
bhaskar 6008 5973 0 06:57 pts/3 00:00:00 grep mumps
[EMAIL PROTECTED]:~/tmp/test$ kill -9 6006
-- Bhaskar
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Gregory Woodhouse
Sent: Thu 11/3/2005 12:56 AM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject: Re: [Hardhats-members] Re: A troublesome and concerning
error.....
On Nov 2, 2005, at 9:39 PM, Gregory Woodhouse wrote:
You'd really have to work at it (at least I did):
Better yet, in session 1 have
USER>ZL ZZLOOP ZP
ZZGREG ;
L +^ZZGREG
F S X=1
USER>J ^ZZLOOP
USER>
USER>L +^ZZGREG
L +^ZZGREG <=== ctrl-C typed AFTER session 2 below
^
<INTERRUPT>^ZZLOOP
USER>
In session 2
~:$ ps -x
PID TT STAT TIME COMMAND
...
454 ?? R 0:28.68 cache ^ZZLOOP
~:$ kill -9 454
~:$
So, a process can seem to wait until kill -9 drops it into direct
mode. Granted it takes some sleight of hand to make this (appear
to?) happen.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Design quality doesn't ensure success, but design failure can ensure
failure."
--Kent Beck
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
