booster: Clean-up handling of log/fstab env variables

Handle two cases when deciding log/fstab file:
1. It turns out that that strdup or strlen doesnt actually
check for NULL before trying to do its thing with the string
so it seg-faults on seeing a NULL char pointer.

2. getenv can return an empty string if the
env var was exported as:
$ export GLUSTEFS_BOOSTER_LOG=

Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

0 files changed, 0 insertions, 0 deletions