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:
Programs in $PATH which are executable by virtue of group permissions, but are not 'other RX', are not found by /usr/bin/which, but can be executed by the shells.

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

How reproducible:
100%

Steps to Reproduce:
1. Remove other RX from any executable in any directory in $PATH
2. Change the group, if needed, to one that you are a member of
3. /usr/bin/which will report it cannot find the changed executable
4. bash and tcsh will both find and execute the program.

Actual results:
/usr/bin/which: no XXX in ( /directory:.... )

Expected results:
full path to first matching executable in $PATH

Additional info:
Discovered while setting up application software for which the license requires that we use a restricted group for access.
Built-in which command for tcsh works as expected.

I cannot reproduce the problem with your steps. 
Could you please add testcase how i can reproduce the problem?

Thanks

I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.
Thanks

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days