Bug 202505
| Summary: | pipe to nonexistent program causes ksh to get SIGSTOP and hang forever | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Todd Allen <redhatbugzilla> |
| Component: | ksh | Assignee: | Karsten Hopp <karsten> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | ||
| 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: | 2006-08-18 09:43:20 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: | |||
ksh-20060214-1.fc5.1 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. It looks like the bug is fixed in 200602014. Thanks. |
Description of problem: If you have "." on the beginning of your PATH, and then you issue a command with a pipe where the last process on the pipe is the name of a nonexistent program, the ksh will get a SIGSTOP, and then drop into the background. If you attempt to resume with the fg command, it will be stopped with another SIGSTOP, ad infinitum. If your ksh was started under an xterm or gnome-terminal instead of under something where dropping into the background is convenient, the xterm or gnome-terminal will just exit when the ksh drops into the background. Usually this happens if I typo a command in the ksh. Having the ksh go AWOL isn't a very nice response to that. :) Version-Release number of selected component (if applicable): ksh-20060124-3 How reproducible: Always Steps to Reproduce: # These executed as root: 1. useradd jojo 2. chsh jojo & specify: /bin/ksh 3. su - jojo # These executed as the new jojo user: 4. export PATH=".:${PATH}" 5. echo it | bogus Actual results: -ksh: bogus: not found [No such file or directory] [1] + Stopped (SIGSTOP) su - jojo Expected results: -ksh: bogus: not found [No such file or directory] Additional info: If you then do this: 6. fg It will respond with this: su - jojo [1] + Stopped (SIGSTOP) su - jojo