|
From: Leif M. <le...@ta...> - 2006-11-11 00:00:49
|
Robey,
Pending review of your 3rd patch about removing signal handling in
the JNI code,
I only did a partial implementation of this patch. I have added support
for SIGUSR1
and SIGUSR2 exactly the same way as the SIGHUP support in 3.2.3.
"If" I remove signal support from the JNI code then the "FORWARD"
mode would
no longer make sense and it would be reused with the "CONTROL" mode
functionality
described in your patch. That way there would be no lost functionality
for users.
Cheers,
Leif
Robey Pointer wrote:
> This is the last and largest patch.
>
> We use signals on our servers to indicate certain control messages.
> For example, HUP is used to mean "reload your config files". The
> latest version of wrapper supports catching HUP (partially) so we've
> had to modify this patch a lot, but the functionality is the same. I
> think this patch may be useful to others too.
>
> A new option for signal handling is created: "CONTROL". If that's set
> as the handler for a signal, a message is sent across the control
> channel indicating the signal, and it arrives in java-land as a
> "controlEvent" with event = WrapperManager.WRAPPER_CTRL_HUP_EVENT (or
> whatever).
>
> This way, the JNI code doesn't have to try to catch signals -- only
> the wrapper process catches them, and passes them on. In addition,
> USR1 and USR2 signals are supported.
>
> robey
|