Bug 1197308

Summary:	do not depend on "killall", use "pkill" instead
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	build	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	anraj, bugs, ndevos
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-30 18:32: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 Niels de Vos 2015-02-28 09:02:31 UTC

Description of problem:
killall is not (by default) available, pkill might be a  better alternative.

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

Comment 1 Worker Ant 2017-03-20 21:27:14 UTC

REVIEW: https://review.gluster.org/16928 (nfs: use pkill on all OS's) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 2 Worker Ant 2017-03-27 11:57:12 UTC

COMMIT: https://review.gluster.org/16928 committed in master by Niels de Vos (ndevos) 
------
commit 16cfe427397d5b8f7a66dfe0b86d9fa5b06de4c1
Author: Niels de Vos <ndevos>
Date:   Mon Mar 20 17:24:37 2017 -0400

    nfs: use pkill on all OS's
    
    'killall' is the only executable that is needed from the psmisc package
    on glusterfs-server installations. NetBSD already uses 'pkill' as
    alternative, this can be used everywhere.
    
    BUG: 1197308
    Change-Id: Ied671a74b735e321f52d99c869627b957aa2bd02
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: https://review.gluster.org/16928
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 3 Shyamsundar 2017-05-30 18:32:08 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/