No error messagse using -u without directory for sock files

[ambsw-technology]

I was trying to upgrade our supervisor directive to use the one in the documentation, but forgot to check that the directory holding the sock files existed.

Supervisor logs were showing that the daphne processes exited and eventually failed with (exit status 0; not expected), but I couldn't find any log messages explaining why (and increasing verbosity did not change anything). I tried pushing supervisor logs (stdout and stderr) to a file and they were empty. I was seeing the same behavior when I tried to run the command on the command line (exits, no messages) but wasn't sure if it was a fair comparison since it wasn't wrapped in the fcgi infrastructure.

Is an error messages supposed to be logged in this case and where should it be found?

[carltongibson]

#263 looks similar. Perhaps some logging (or an exit) added if socket creation fails somehow? Happy to see input there.