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.
Description of problem:
In RHEL7, I could enable the systemd /tmp tmpfs mount with:
$ systemctl enable tmp.mount
This does not work in RHEL8, and the systemd /tmp mount is not activated automatically either.
In RHEL7, there is an '[Install]' section in the tmp.mount systemd file which makes it possible to enable it. This section is missing in RHEL8.
So - what is the recommended approach to set /tmp as tmpfs mount in RHEL8? (I know I can do it via fstab, but I thought systemd was the way to do it nowadays).
Version-Release number of selected component (if applicable):
systemd-239-8.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. systemctl enable tmp.mount
2.
3.
Actual results:
Output from systemctl:
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Expected results:
/tmp should be mounted as tmpfs by systemd
Additional info:
(In reply to adam winberg from comment #0)
> So - what is the recommended approach to set /tmp as tmpfs mount in RHEL8?
> (I know I can do it via fstab, but I thought systemd was the way to do it
> nowadays).
'systemctl enable tmp.mount' should work, it's a bug. Thanks for reporting it!
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:3592