[Bugs] [Bug 1258561] New: Gluster puts PID files in wrong place

[bugzilla at redhat.com]

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

            Bug ID: 1258561
           Summary: Gluster puts PID files in wrong place
           Product: GlusterFS
           Version: mainline
         Component: unclassified
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: jdarcy at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



There's not a lot of consistency here, but most of the PID files for
Gluster-related services seem to be going into $sharedstatedir (i.e.
/var/lib/gluster).  This is wrong.  First it's wrong because it violates the
principle of keeping *configuration* separate from *run time state*.  Second
it's wrong because it violates standards which respect this separation.  I
couldn't find anything in Fedora/RHEL packaging guidelines, but I did find the
GNU document describing what these automake/autoconf variables are supposed to
mean.

https://www.gnu.org/prep/standards/html_node/Directory-Variables.html

According to that, what we're supposed to be using for per-node run-time state
is $runstatedir (i.e. /var/run) which is itself supposed to be derived from
$localstatedir (i.e. /var).  The doc specifically cites PID files as an example
of what should be there.

One user already got bitten by this, because they were saving/restoring
/var/lib/gluster across a server migration and ended up including bogus PID
files.  Arguably their configuration/methodology is one we do not support, but
that doesn't mean we should add extra obstacles that violate both standards and
common sense.

(Component is unclassified because this affects multiple components.  I suggest
that fixes in specific components be tracked by cloning this bug and adding a
depencency.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.