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: The -l option of "rlog" doesn't restrict searches to the specified user when checking for file locks.
Version-Release number of selected component (if applicable):
5.9.0-5
How reproducible: Consistently.
Steps to Reproduce:
Assume two users, user1 and user2.
[user1] $ mkdir -p /tmp/RCS
[user1] $ cd /tmp
[user1] $ chmod 777 RCS
[user1] $ touch file1 file2
[user1] $ ci file1 file2
[user1] $ co -l file2
[user1] $ su - user2
[user2] $ cd /tmp
[user2] $ touch file3
[user2] $ ci file3
[user2] $ co -l file3
Actual results:
When running "rlog -R -L -luser2 RCS/*", file2 and file3 are listed.
Expected results:
When running "rlog -R -L -luser2 RCS/*", only file3 should be listed.
Additional info:
This issues seems to be present regardless of whether a local filesystem or one attached to NFS is used.
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-2020:1013
Description of problem: The -l option of "rlog" doesn't restrict searches to the specified user when checking for file locks. Version-Release number of selected component (if applicable): 5.9.0-5 How reproducible: Consistently. Steps to Reproduce: Assume two users, user1 and user2. [user1] $ mkdir -p /tmp/RCS [user1] $ cd /tmp [user1] $ chmod 777 RCS [user1] $ touch file1 file2 [user1] $ ci file1 file2 [user1] $ co -l file2 [user1] $ su - user2 [user2] $ cd /tmp [user2] $ touch file3 [user2] $ ci file3 [user2] $ co -l file3 Actual results: When running "rlog -R -L -luser2 RCS/*", file2 and file3 are listed. Expected results: When running "rlog -R -L -luser2 RCS/*", only file3 should be listed. Additional info: This issues seems to be present regardless of whether a local filesystem or one attached to NFS is used.