Bug 9110
Summary: | wild card asterisk does not function under selected conditions | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John B. Brown <jbb> |
Component: | fileutils | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-07 18:26:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John B. Brown
2000-02-04 03:39:31 UTC
This wild card problem also applies to ? as a character wild card. It also happens any time I use a wild card under the conditions described above; on a very weird basis. May this also be a bash problem? Since this original report I've recompiled the kernel and reinstalled it; rpm'd the kernel in from the CD 1, and compiled linux 2.2.13 w/crypto and installed that. No change in the wild card condition. Of course, the support persons original guess may be valid; PAM. So then what's the solution? I know nothing about PAM. We can't reproduce it anywhere. Are you sure your user has rx access to the directory you're trying to list? directories at 777; ls * says no such file. run script, condition disappers while script runs. su to self, condition disappears. exit from su, condition reappears. log in as root, ls * sometimes works, sometimes doesn't. su to user, condition appears. exit su, condition disappears. enter user directory (777) su to user, condition appears. exit su condition disappears. recompile linux w/o networking, condition as above. recompile w/ networking, condition as above. logging in to the non networking box caused a PAM message to appear prior to the prompt appearing, both as root and as user. What is that??? This bug is not a fileutils bug. Recompiling from various archived source doesn't change the problem. Recompiling bash from various source also makes no change. Recompiling the kernel both red hat source and kerneli source makes no change. I'm going to reenter the problem as a kernel bug. The problem was with the wild card expander. alias ls='/bin/ls -aFC $@' worked for 5.2 and 6.0 to expand wild cards and any text that followed ls. Now the expander must be $*. There has been some change! It would be nice to know what. And Why! |