Description of problem:

When logging is not inited using gf_log or gf_msg gives an illusion that message is being logged but it isn't.

Print all the critical info to stdout/stderr and don't use gf_log or gf_msg before logging_init.


How reproducible:
Always


Steps to Reproduce:
1. Delete contents of /etc/glusterfs
2. start glusterd on command line.


Actual results:
just a usage format is printed on screen without telling what went wrong.

Expected results:
We should also print on screen what we are trying to log here.
gf_msg ("glusterfs", GF_LOG_CRITICAL, errno, glusterfsd_msg_16);


This is one example, there are probably few others. Let this bug cover all such
occurences.