Description of problem: On default Fedora 19 install, and after updating, glusterfsd enters failed state.


Version-Release number of selected component (if applicable):
glusterfs-3.4.0-2.fc19.x86_64
glusterfs-server-3.4.0-2.fc19.x86_64
glusterfs-geo-replication-3.4.0-2.fc19.x86_64
glusterfs-api-3.4.0-2.fc19.x86_64
glusterfs-fuse-3.4.0-2.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora 19 and reboot. Optionally update to current, then rebot.
2. journalctl -b -u glusterfsd
3.

Actual results:

Jul 26 22:43:43 f19sv1.local systemd[1]: Starting GlusterFS an clustered file-system server...
Jul 26 22:43:43 f19sv1.local glusterfsd[282]: [2013-07-27 04:43:43.959907] C [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile failed (No such file or directory)
Jul 26 22:43:43 f19sv1.local GlusterFS[282]: [2013-07-27 04:43:43.959907] C [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile failed (No such file or directory)
Jul 26 22:43:43 f19sv1.local glusterfsd[282]: USAGE: /usr/sbin/glusterfsd [options] [mountpoint]
Jul 26 22:43:43 f19sv1.local systemd[1]: glusterfsd.service: control process exited, code=exited status=255
Jul 26 22:43:43 f19sv1.local systemd[1]: Failed to start GlusterFS an clustered file-system server.
Jul 26 22:43:43 f19sv1.local systemd[1]: Unit glusterfsd.service entered failed state.


Expected results:
It's installed and enabled by default, so it should successfully start. Alternatively if it can't be made to successfully start unless configured first, it should be disabled by default to avoid the failure status message on every boot.

Additional info:
Bug 980683, AVC denial of glusterfs has been fixed, no AVC denial is occurring so that's not what's causing this failure to start.