Re: [ovs-dev] [PATCH 1/5] fatal-signal: Fatal signal handling for Windows.

2014-02-26 Thread Ben Pfaff
On Wed, Feb 26, 2014 at 11:40:54AM -0800, Gurucharan Shetty wrote: > On Wed, Feb 26, 2014 at 11:24 AM, Ben Pfaff wrote: > > On Wed, Feb 26, 2014 at 10:51:56AM -0800, Gurucharan Shetty wrote: > >> Windows does not have a SIGHUP or SIGALRM. It does have > >> a SIGINT and SIGTERM. The documentation a

Re: [ovs-dev] [PATCH 1/5] fatal-signal: Fatal signal handling for Windows.

2014-02-26 Thread Gurucharan Shetty
On Wed, Feb 26, 2014 at 11:24 AM, Ben Pfaff wrote: > On Wed, Feb 26, 2014 at 10:51:56AM -0800, Gurucharan Shetty wrote: >> Windows does not have a SIGHUP or SIGALRM. It does have >> a SIGINT and SIGTERM. The documentation at msdn says that >> SIGINT is not supported for win32 applications because

Re: [ovs-dev] [PATCH 1/5] fatal-signal: Fatal signal handling for Windows.

2014-02-26 Thread Ben Pfaff
On Wed, Feb 26, 2014 at 10:51:56AM -0800, Gurucharan Shetty wrote: > Windows does not have a SIGHUP or SIGALRM. It does have > a SIGINT and SIGTERM. The documentation at msdn says that > SIGINT is not supported for win32 applications because > WIN32 operating systems generate a new thread to specif

[ovs-dev] [PATCH 1/5] fatal-signal: Fatal signal handling for Windows.

2014-02-26 Thread Gurucharan Shetty
Windows does not have a SIGHUP or SIGALRM. It does have a SIGINT and SIGTERM. The documentation at msdn says that SIGINT is not supported for win32 applications because WIN32 operating systems generate a new thread to specifically handle Ctrl+C. This commit handles SIGTERM for Windows. The documen