glusterd: glusterd is crashed at the time of stop volume

Problem: glusterd is crashed at the time of stop volume due to 
         overflow of pidfile array after build rpm with default options.

Solution: To avoid the crash update the pidfile array size.

Test:    To test the patch followed below procedure
         1) Setup 1*2 environment and start the volume
         2) Stop the volume
         Before apply the patch glusterd is crashed.

Note:  The crash is happened only after build rpm with rpmbuild -ba 
       <spec> because _FORTIFY_SOURCE is enabled. This option tries to 
       figure out possible overflow scenarios like the bug here and 
       crash the process.

> BUG: 1420202
> Change-Id: I58a006bc0727843a7ed02a10b4ebd5dca39eae67
> Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
> Reviewed-on: https://review.gluster.org/16560
> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>1420606
> Smoke: Gluster Build System <jenkins@build.gluster.org>
> Reviewed-by: N Balachandran <nbalacha@redhat.com>
> Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
> CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
> (cherry picked from commit 9ac193a19b0ca6d6548aeafa5c915b26396f8697)

Change-Id: I4bcfe830e789a9b95fbcace4495bfda17dca0269
BUG: 1420606
Reviewed-on: https://review.gluster.org/16571
Tested-by: MOHIT AGRAWAL <moagrawa@redhat.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

0 files changed, 0 insertions, 0 deletions