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.
DescriptionMichal Sekletar
2018-03-01 12:16:31 UTC
Description of problem:
Every PAM session has scope unit associated with it. In the session creation process, we also create stub unit file for the given scope unit alongside drop-in configuration for it. However, when the session ends we don't delete this stub unit file.
Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.7
How reproducible:
always
Steps to Reproduce:
1. ssh into the machine
2. cat /run/systemd/system/session-${XDG_SESSION_ID}.scope
3. log out
4. ssh back again
5. env | grep XDG_SESSION_ID (session ID should be different)
6. verify that old session scope unit file is still present
Actual results:
Old session-${XDG_SESSION_ID}.scope unit file present in /run/systemd/system
Expected results:
Unit file is deleted when session ends
Additional info:
https://github.com/lnykryn/systemd-rhel/pull/186
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/RHBA-2018:3245
Description of problem: Every PAM session has scope unit associated with it. In the session creation process, we also create stub unit file for the given scope unit alongside drop-in configuration for it. However, when the session ends we don't delete this stub unit file. Version-Release number of selected component (if applicable): systemd-219-42.el7_4.7 How reproducible: always Steps to Reproduce: 1. ssh into the machine 2. cat /run/systemd/system/session-${XDG_SESSION_ID}.scope 3. log out 4. ssh back again 5. env | grep XDG_SESSION_ID (session ID should be different) 6. verify that old session scope unit file is still present Actual results: Old session-${XDG_SESSION_ID}.scope unit file present in /run/systemd/system Expected results: Unit file is deleted when session ends Additional info: https://github.com/lnykryn/systemd-rhel/pull/186