Awa 'daemons' do not follow the Forking Readiness Protocol

[DavidAntliff]

Affects 0.1.9.

Services are considered ready after the MainPID exits (after the double fork), allowing for time to setup sockets or other resources needed to handle client requests (e.g. a database server or a web server). Awa daemons do not do this, so dependent services may fail to startup properly, as their dependencies aren't actually ready when systemd declares them to be.

http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/unix-daemon-readiness-protocol-problems.html