Bug 1476794 - glusterfs and /var/run
Summary: glusterfs and /var/run
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: glusterfs
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-31 13:27 UTC by dac.override
Modified: 2018-09-06 10:54 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-09-06 10:54:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1484440 0 unspecified CLOSED packaging: /run and /var/run; prefer /run 2021-02-22 00:41:40 UTC

Internal Links: 1484440

Description dac.override 2017-07-31 13:27:32 UTC
Description of problem:

please install the "gluster" directory to "/run" instead of "/var/run"

"/var/run" is legacy since about 5 years.

ironically you did it right in /usr/lib/tmpfiles.d/gluster.conf

Comment 1 Kaleb KEITHLEY 2017-07-31 13:39:10 UTC
The ironically comment was unnecessary and unprofessional.

Comment 2 dac.override 2017-07-31 13:42:51 UTC
Didn't mean it that way. Sorry about that

Comment 3 dac.override 2017-07-31 13:47:28 UTC
In my defense though, this is not my profession. As a matter of fact i am not employed at all. I try to do this for fun, but it is not exactly enjoyable to have to remind as many package mantainers as i have to about /var/run being legacy for about 5 years.

Comment 4 Jan Kurik 2017-08-15 07:25:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 5 Joe Julian 2017-08-23 17:29:46 UTC
For posterity, FHS 3.0, published March 19, 2015, does not go so far as to say "deprecated". https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html

IMHO it would be good to only use /run and any changes made to the code base that touches code that uses that directory should be updated accordingly as part of other development, but it seems to me that it's a low priority otherwise.

It would seem to be a good opportunity for a code contribution from the community though. Is that something you think you could do, Jan?

Comment 6 Joe Julian 2017-08-23 17:32:30 UTC
Oops, I meant dac.override, not Jan.

Comment 7 dac.override 2017-08-23 17:43:19 UTC
These bugzilla's are targeting Fedora packaging. I am not worried about the code-base other than rpm, systemd and tmpfiles configuration (which is all fedora specific)

I have my own project to work on (dont have the time to deal with this tree-wide). The reason I am requesting these changes is that I do not want to be forced to support /var/run. My requirements are very specific.

RPM, systemd and systemd-tmpfiles are SELinux-aware and when rpm installs objects to /var/run, or when systemd creates a socket-activated-socket in /var/run, or when systemd-tmpfiles creates an object in /var/run , the libselinux code will ask the policy what context to associate with /var/run/$FILE and from a policy perspective i dont want to have to polute the policy just to keep faulty RPM, systemd socket units, systemd-tmpfiles snippets *working*

In other words: i am only concerned about RPM specs, systemd socket units and systemd-tmpfiles snippets, and only for the packages that i install. glusterfs is pulled in by qemu.

Comment 8 Kaleb KEITHLEY 2017-08-23 18:07:25 UTC
Most of the latest packages, both in Fedora and on download.gluster.org have addressed the /var/run vs. /run issue. I just haven't closed the BZ yet (and wasn't going to until after the impending 3.12 release.)

If someone wants the gluster sources to fix any uses of /var/run you should open another BZ for that.

Comment 9 Anoop C S 2018-09-06 10:54:02 UTC
GlusterFS 3.12 (and minor updates) packages are already available in stable repositories. Therefore closing the bug report as per comment #8.


Note You need to log in before you can comment on or make changes to this bug.