Bug 860466

Summary:	[enhancement] The self-heal daemon should call itself glustershd
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	bugs, joe, ksubrahm
Target Milestone:	---	Keywords:	Reopened, RFE, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 09:37:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joe Julian 2012-09-25 21:49:01 UTC

The self heal daemon should change it's process name to glustershd so it can be more easily managed. It would be nice to be able to use process tools to, send signals to the self-heal daemon without having to figure out which glusterfs process was the right one.

I don't think we need another symlink, just have a way (maybe a volfile setting?) that allows the process to set it's argv[0].

Comment 1 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC

because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.

Comment 2 Pranith Kumar K 2016-06-15 07:37:21 UTC

Joe,
    Are you saying we should have symlink with glustershd -> glusterfsd so that the name in ps comes as glustershd?

Pranith

Comment 3 Joe Julian 2016-07-25 13:05:51 UTC

Answered in original description.

Comment 4 Kaushal 2017-03-08 10:50:28 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

Comment 5 Karthik U S 2018-11-19 09:37:08 UTC

We are closing this bug as WONTFIX mainly as we are not planning to work on this  this with priority in near future. Please feel free to reopen if you feel this needs to be prioritized and fixed soon.