Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1730721

Summary: absolute path used for default state and runtime dir by default
Product: Red Hat Enterprise Linux 8 Reporter: Luboš Uhliarik <luhliari>
Component: httpd-2.4-moduleAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Branislav Náter <bnater>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: bnater, jorton
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1828828 (view as bug list) Environment:
Last Closed: 2019-11-05 21:12:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luboš Uhliarik 2019-07-17 12:58:02 UTC
Description of problem:
Instead of patching upstream config.layout, supply are own config.layout with proper paths + change paths for runtime dir and state dir. 

Previous values of runtime and state dir were:

runtimedir: /run/httpd
statedir: /var/lib/httpd

NEW values:

runtimedir: /etc/httpd/run
statedir: /etc/httpd/state

Also relative paths are correctly set. The whole change looks like:

diff of old/new /usr/include/httpd/ap_config_layout.h:
53,54c53,54
< #define DEFAULT_EXP_RUNTIMEDIR "/run/httpd"
< #define DEFAULT_REL_RUNTIMEDIR "/run/httpd"
 ---
> #define DEFAULT_EXP_RUNTIMEDIR "/etc/httpd/run"
> #define DEFAULT_REL_RUNTIMEDIR "run"
59,60c59,60
< #define DEFAULT_EXP_STATEDIR "/var/lib/httpd"
< #define DEFAULT_REL_STATEDIR "/var/lib/httpd"
 ---
> #define DEFAULT_EXP_STATEDIR "/etc/httpd/state"
> #define DEFAULT_REL_STATEDIR "state"


ServerRoot is set to /etc/httpd, but for compatibility there are symlinks in /etc/httpd/{state,run}.

When ServerRoot is set by -d param when executing httpd, relative paths will be used e.g. $ServerRoot/state and $ServerRoot/run.


Version-Release number of selected component (if applicable):
httpd-2.4.37-14

How reproducible:
TBD

Steps to Reproduce:
1. TBD

Actual results:
- when -d param is used, absolute paths /var/lib/httpd and /run/httpd are used.


Expected results:
- when -d param is used, httpd should use $ServerRoot/state and $ServerRoot/run dirs.

Additional info:
I will supply reproducers or TC.

Comment 6 errata-xmlrpc 2019-11-05 21:12:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3436