logging: extra message when systemd fails to provide socket during service startup
When kresd is running under systemd with socket activation and systemd fails to provide the socket, kresd falls back to attempt to bind to a port directly. This fails, because the service doesn't have these privileges. When examining the service log, the user finds:
kresd: [system] bind to '127.0.0.1@53' Permission denied kresd: [system] bind to '::1@53' Permission denied kresd: [string "init"]:12: error: not listening on any interface, exiting... systemd: email@example.com: Main process exited, code=exited, status=1/FAILURE
Which is misleading and provides no useful pointers to what has actually gone wrong. The log should explicitly mention that systemd socket wasn't provided and make it clear that this is most likely the cause of the issue.