Bug 804293 - [5e50175f56d05ab6c1295b0e0f0c11695e49c277]: change brick-with-valgrind option to run-with-valgrind
Summary: [5e50175f56d05ab6c1295b0e0f0c11695e49c277]: change brick-with-valgrind option...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Vinayaga Raman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-17 13:01 UTC by Rahul C S
Modified: 2014-03-31 01:28 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:44:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: 1f3a0dd4742a2fcd3215aee4a5e22125d7ea4f4d
Embargoed:

Attachments (Terms of Use)

Description Rahul C S 2012-03-17 13:01:02 UTC 
Description of problem:
brick-with-valgrind does not make much sense because all the glusterfs/glusterfsd server processes are run with valgrind. So changing the option from brick with valgrind to run-with-valgrind.

Also the log name is misspelled as valgrnd instead of valgrind.
Comment 1 Anand Avati 2012-03-18 06:45:10 UTC 
CHANGE: http://review.gluster.com/2965 (Change option brick-with-valgrind to run-with-valgrind) merged in master by Anand Avati (avati)
Comment 2 Rahul C S 2012-04-05 09:41:00 UTC 
Changes working fine. All server processes start with valgrind with this option.
Note You need to log in before you can comment on or make changes to this bug.