Comment 4 for bug 1803182

I've successfully tested use of USR1 to gracefully shut down osrf-websocket-stdio backends, but I'm not clear how one goes about cleanly shutting down the websocketd process itself (or more precisely, putting it in a state where it won't accept any more connection requests while the backends are gracefully shutting down). Bill, do you have any insight on that?

Of course, if something like ldirectord or NGINX is being used as a proxy and/or load balancer, I can envision ways to make the load balancer stop directing new connections to a websocketd instance that is being shut down, but I'm curious whether there's any way make websocketd itself do it.