#44 Startup failure notice

[Amy Lear]

Currently, if proto can't bind to a socket (such as it
being in use) it doesn't bother letting you know
there's a problem. Instead, it just silently exits,
without putting anything in any logs to indicate a problem.
Could something go into a log to indicate that
something didn't go right?