Re: 1.3, kernel 2.6, signals

Interestingly, I tried a 2.6.4 kernel just now (after doing all of my
testing on 2.6.3) and it still does not work with the JVMs I listed.

It must be a kernel option, library version, or something else I am doing
on these systems that is producing the different behavior.

At 21:38 on Mar 18, Hui Huang shook the earth with:

> Hi Nicole,
>
> I tested your code. It works fine on my machine with 2.6.4. I
> tested Sun JDK 1.3.1fcs, 1.3.1_10, 1.3.1_11, 1.4.2fcs, 1.4.2_03
> and 1.5beta. SignalTest is able to catch HUP, TERM, INT.
>
> That said, I'd like to point out that the Java level signal API
> is private interface. Its sole purpose is to implement the shutdown
> mechanism (see Runtime.addShutdownHook). The interface may change
> or get dropped completely without notice in future JDK. So use at
> your own risk. (If you really want to catch signals, it's better
> to write JNI code; signals have well-defined behavior at C level,
> but not at Java level).
>
> regards,
> -hui
>
> nicole wrote:
> > Ah, the IBM JDK was holding the signals for the JVM, that explains why
> > that didn't work (had to use -Xrs).
> >
> > Works with 2.6:
> > IBM 1.3.1-6 (with -Xrs)
> > Sun 1.4.2_03 (no -Xrs)
> >
> > Does Not Work with 2.6:
> > Blackdown 1.3.1
> > Sun 1.3.1_10
> > Sun 1.3.1_11
> >
> > Untested:
> > Blackdown 1.4.x
> > IBM 1.4.x


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]