I always just go with (1). This problem occurs to me and always bugs
me a little, but I file it under "issues the day is too short to worry
about". In practice when you see this in the logs
starting server on port 4567
it's clear enough what happened.
On Thu, Nov 9, 2017 at 12:16 PM, Kevin
I want to start an HTTP server, and then once it's started, log a message
that the server has started. Here are the options for doing that:
- log ahead of time. The message gets logged before the server starts
listening on a socket, which means you might get the message and then an
error
