Bug 764701 (GLUSTER-2969)

Summary: add --pidfile option
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: glusterdAssignee: Lakshmipathi G <lakshmipathi>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joe Julian 2011-05-31 21:45:04 UTC 
Your init script has the unwelcome side effect of killing client mounts due to the fact that it's trying to kill it's nfs child. Blanket killall statements are not the best way to handle this anyway.

Have glusterd take a --pidfile option/an option in glusterd.vol to write it's own pid, as well as the child pid's, to a specified file as those children are spawned. Remove the pids from that file as children are killed (for instance when a volume is stopped).
Comment 1 Anand Avati 2011-06-08 15:17:33 UTC 
PATCH: http://patches.gluster.com/patch/7395 in master (build : use pid file to kill nfs process)
Comment 2 Anand Avati 2011-06-08 15:19:32 UTC 
PATCH: http://patches.gluster.com/patch/7396 in release-3.2 (build : use pid file to kill nfs process)
Comment 3 Lakshmipathi G 2011-06-10 07:38:09 UTC 
installed 3.2.1qa4 and mounted client processes ,then did /etc/init.d/glusterd stop - kills only the glusterd and nfs process and client process is still alive.
Comment 4 Anand Avati 2011-06-17 12:34:20 UTC 
PATCH: http://patches.gluster.com/patch/7541 in release-3.1 (build : use pid file to kill nfs process)