[Bugs] [Bug 1480459] Gluster puts PID files in wrong place

bugzilla at redhat.com bugzilla at redhat.com
Sat Aug 12 13:38:34 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1480459



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18023 committed in release-3.12 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 22ac7241b2f8c1bb3db2678b8b6b9a364f14876c
Author: Gaurav Kumar Garg <garg.gaurav52 at gmail.com>
Date:   Wed Mar 2 17:42:07 2016 +0530

    glusterd: Gluster should keep PID file in correct location

    Currently Gluster keeps process pid information of all the daemons
    and brick processes in Gluster configuration file directory
    (ie., /var/lib/glusterd/*).

    These pid files should be seperate from configuration files.
    Deletion of the configuration file directory might result into serious
problems.
    Also, /var/run/gluster is the default placeholder directory for pid files.

    So, with this fix Gluster will keep all process pid information of all
    processes in /var/run/gluster/* directory.

    > BUG: 1258561
    > Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    > Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    > Reviewed-on: https://review.gluster.org/13580
    > Tested-by: MOHIT AGRAWAL <moagrawa at redhat.com>
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    > cherry pick from commit 220d406ad13d840e950eef001a2b36f87570058d

    BUG: 1480459
    Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
    Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    Reviewed-on: https://review.gluster.org/18023
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PLLxIx19fB&a=cc_unsubscribe


More information about the Bugs mailing list