Comment 1 for bug 1870534

I think this is going to be unavoidable -- it'd be *nice* if we could get a `Connection: close` header out, and we might even be able to do that for writes or even account/container reads. But any connections where we've already sent headers when the SIGUSR1 was received are out of luck -- the server's hanging up and there's no good way to signal that to the client.