I have an application that has signal handlers registered for signals 11, 15, and 2. When these signals are received, I print out that I caught the signal, call some "dump to disk" functions for what's in memory, then I System.exit().
I upgraded my kernel to version 2.6, and now it looks like these signals aren't being caught anymore -- sort of. Previously each time I sent one of those signals over, it would print (for example, "Caught INT, cleaning up"), call what I needed, and exit. Before the signal handlers were introduced, these signals just killed the JVM (as expected). Now, when I send a signal, it does *not* print, but it does not exit either. It's like the JVM is catching the signal, but is not passing it on to my code. I've been using blackdown 1.3.1, but as a test I switched to Sun's 1.3.1_10 and am still having the same problem. Because of SSL certificate changes in 1.4, I can't switch up just yet, but I really want some of the OS-side functionality of kernel 2.6. I have upgraded my system applications as per the Documentation/Changes file in the kernel source. Really this just entailed upgrading procps, e2fsprogs, and util-linux, as my other applications were at sufficient versions. I am running debian stable, entirely stock, except for those few applications that I upgraded hoping they would fix the problem, and the kernel (2.6.3). I assumed the problem is related to NPTL, so I have set the LD_ASSUME_KERNEL variable to both "2.2.5" and "2.4.1" to no avail. I thought perhaps I needed to upgrade my libc6, but I don't know that that is the case. Right now it's running 2.2.5-11.5. Any ideas? I'll try anything at this point, I'd really like to keep my kernel. Even if I just have the answer and decide to stick with 2.4 for now, I'd at least like to know :o) Thanks, -nicole ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
