barriers.exe on windows will not completely handle events such as a client connecting or ctrl+c. with --debug up high enough you might see that it knows that something happened but it will not follow through on dealing with it.

to reproduce:

1. start barriers.exe from cmd so you have keyboard input (get nice command line from GUI log pane) and set --debug to at least INFO
2. once it's idling, hit ctrl+c

notice that it acknowledges the command with the following line:

• INFO: got shutdown signal

but it does not react to it otherwise by shutting down.