I think the shutdown here doesn't do much; or at least, not what you hope.

It works in the HTTP API because the underlying `net/http` module's `Serve()` method has some intelligent handling of `Accept()` failures: http://golang.org/src/pkg/net/http/server.go?s=45477:45526#L1618

In short it determines if it's a temporary or permanent failure, and it aborts the accept loop on permanent failures. That allows the `Serve()` method to exit, which ends up triggering the `defer` to send the true on the shutdown channel.

I haven't fully thought through the implications of shutdown in InfluxDB (just started looking at the code today) so I don't know what the right solution is.