If --service is used, it still creates the exit_event just like before, but it also creates the new events with the same name as the exit_event but appends the signal name like, exit_event_SIGHUP.
It always creates the new signals in non signaled state. Some things to consider that I havn't thought through fully.1. To have the new events checked I added them in wait_signal() in event.h. Was this the correct place? Or do the diffent events need to be added to the "check event list" at a diffrent time?
2. I modified the win32_service_interrupt() function to return the signal value instead of just true/false. This means that this function will now return "true" for all signals, not only sigterm. Will that cause any problems?
3. Do we need to block the new events from beeing checked at some time?4. Do you have plans to give SIGINT a diffrent functionallity than SIGTERM in the future? If so, do you think we should add a event for SIGINT also now?
Apart from that I think it works well. I can now send all the signals from my GUI and it does not break compatibility with existing software.
-- _____________________________________________________________ Mathias Sundman (^) ASCII Ribbon Campaign OpenVPN GUI for Windows X NO HTML/RTF in e-mail http://www.nilings.se/openvpn / \ NO Word docs in e-mail
openvpn-2.0_beta15-events.diff
Description: Binary data
