Bug 2883
Summary: | the bash process started with xterm dont die when X server is killed. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | n.lathiotakis |
Component: | distribution | Assignee: | David Lawrence <dkl> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
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: | 1999-05-19 14:39: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: |
Description
n.lathiotakis
1999-05-17 19:01:46 UTC
I believe this is a dup of bug #2767, which I entered on 5/14/99. I don't know if this is related, but I've noticed that if you start an xterm without the "&" (i.e. it's in the shell foreground), then hit Ctrl-c, it won't die, but it will freeze up. I'm almost 100% sure that this situation should, and normally does, just kill the xterm. |