Gregory wrote: > >On Nov 2, 2005, at 6:52 PM, Bhaskar, KS wrote: > >> >> If a 9 (KILL) is results in GT.M dropping you to the direct mode >> prompt, it would be a bug in the UNIX/Linux kernel not GT.M! A >> process cannot trap/block a kill -9 because the process never sees >> it. The kernel simply makes the process cease to exist. >> >> There's no bug here that the evidence points to. >> >> -- Bhaskar > >You'd really have to work at it (at least I did): > >In session 1: > >USER>ZL ZZLOOP ZP >ZZLOOP ; > F S X=1 > > >USER>J ZZLOOP > >USER>w "I am alive" <== Note: This command is executed until AFTER >session 2 completes >I am alive >USER>h >~:$ > >In session 2: > > 426 ?? R 0:50.81 cache ZZLOOP^ZZLOOP > 420 p1 S 0:00.03 -bash > 423 p1 S+ 0:00.03 /Applications/Cache/bin/cache -s / >Applications/Cache/ > 429 p2 S 0:00.03 -bash >~:$ kill -9 426
That does not look like GT.M to me. Neither does it look like a Linux bug. It looks like you started in a MUMPS shell and then used the JOB command to start a second MUMPS (cache) process that you then killed and the parent process continued on... as it should. As I see it, there would be a security issue here only if you demonstrated a way for users to escalate their privileges so as to get a shell prompt (GT.M or Linux) that wasn't intended by the sysadmin. --------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) ------------------------------------------------------- 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
