> If you make sure, you do not mask your SIGUSR1 and SIGUSR2,
>you should be able to run fine. However, there is one caveat. Linux
>threads use SIGUSR1 and SIGUSR2 for their internal
>communication in some products. If your >product also uses them,
>you should see for alternatives.
Actually, I believe the Linux thread support in glibc no longer uses SIGUSR1
& 2.
It's more likely his problem is coming from masking all those signals (bad,
bad, bad) which the JVM needs to have available to it.
The AOLServer's sigwait() is essentially the source of your problems. I'm
not sure how you'd fix it, as I'm not familiar with the AOLServer code.
--Chris
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
