Description of problem:

Since the glusterd.service is set with "Type=forking", if glusterd fails to fork within the default 90 seconds, the service fails while leaving glusterd running.

If glusterd eventually has quorum established, it will start up successfully and background itself leaving the cluster healthy but systemd status will show that the service has failed to start.

How reproducible:
always

Steps to Reproduce:
1. Set up server quorum
2. Boot a server on a distro that uses systemd
3. wait 90 seconds

Actual results:
systemd service fails and leaves glusterd running

Expected results:
I think my expectation is that glusterd will daemonize and continue to try in the background. Either that or we should just run glusterd as a foreground process  when started by systemd and change Type to simple.

Additional info: