Your suggestion of a log message is probably the best approach. Thanks, Alan.
-----Original Message----- From: Victor Orlikowski [mailto:v...@duke.edu] Sent: Wednesday, July 20, 2016 11:36 AM To: FORDYCE,ALAN (K-Scotland,ex1) <alan_ford...@keysight.com> Cc: ryu-devel@lists.sourceforge.net Subject: Re: [Ryu-devel] KeyboardInterrupt (ctrl-c) and RYU Also - should be obvious - but include a comment on the pass, explaining that you're "papering over" the fact that eventlet doesn't properly wrap the KeyboardInterrupt inside select()/poll()/epoll(). Another suggestion: instead of a pass, a log message, at debug level (or whatever desired default priority), that notes that Ctrl-C was received and applications are terminating. Best, Victor -- Victor J. Orlikowski <> vjo@[cs.]duke.edu > On Jul 20, 2016, at 11:20 AM, Victor Orlikowski <v...@duke.edu> wrote: > > Suggest just silently swallowing the KeyboardInterrupt (with a "pass"), since > the finally block will cover the close(). ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
