Bug 1335731

+++ This bug was initially created as a clone of Bug #1331042 +++

Description of problem:
Currently, we always exit mount process with the pid as the exit number
which is return value of the waitpid(), it is not the exit value of the
child process

Version-Release number of selected component (if applicable):
mainline

Expected results:
exit with actual status/code

--- Additional comment from Vijay Bellur on 2016-04-27 10:10:06 EDT ---

REVIEW: http://review.gluster.org/14094 (glusterfsd: fix to return actual exit status on mount process) posted (#1) for review on master by Prasanna Kumar Kalever (pkalever)

--- Additional comment from Vijay Bellur on 2016-04-29 09:24:02 EDT ---

COMMIT: http://review.gluster.org/14094 committed in master by Jeff Darcy (jdarcy) 
------
commit 36d025ef6f178ce5d8c6f7fa09e1cf236976b5ea
Author: Prasanna Kumar Kalever <prasanna.kalever>
Date:   Wed Apr 27 19:29:09 2016 +0530

    glusterfsd: fix to return actual exit status on mount process
    
    Problem:
    Currently, we always exit mount process with the pid as the exit number
    which is return value of the waitpid(), it is not the exit value of the
    child process
    
    Solution:
    Extract the actual exit code/status in case if the child terminated normally,
    that is, by calling exit(3) or _exit(2), or by returning from main()
    
    Change-Id: Iefec6e27b5a5a98a22f016e49967978853662e37
    BUG: 1331042
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever>
    Reviewed-on: http://review.gluster.org/14094
    Tested-by: Prasanna Kumar Kalever <pkalever>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Jeff Darcy <jdarcy>