Bug 111649
| Summary: | shell must be reset after using vtysh | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ted Kaczmarek <tedkaz> |
| Component: | zip | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-12-13 23:23:33 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: | |||
That will be a bug in vtysh, not bash. This problem occurs with ssh also, after connecting to a RH9 box via ssh, I get the same quirks where the shell has to be reset. It appears that some signals get messed up, reseting the shell will also fix every time. Again with zsh I do not see the problem. 'Some signals get messed up'? It is a signal handling problem in the *application*, yes, in that it doesn't return the terminal to the mode it found it in. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031129 Epiphany/1.0.6 Description of problem: Zebra daemon vtysh access from bash, shell will freak out. Issuing reset corrects the problem. Version-Release number of selected component (if applicable): bash-2.05b-31 How reproducible: Always Steps to Reproduce: 1.Fire up zebra daemon 2.vtysh, en, wr t 3.exit vtysh, hit enter 3 times Actual Results: tarkus# exit [root@tarkus root]# [root@tarkus root]# [root@tarkus root]# [root@tarkus root]# Expected Results: [root@tarkus root]# [root@tarkus root]# [root@tarkus root]# [root@tarkus root]# Additional info: Zsh does not exhibit this behavior, so it could be classified as a workaround :-) [root@tarkus root]# cat /etc/sysconfig/i18n LANG="en_US" SUPPORTED="en_US.UTF-8:en_US:en" SYSFONT="latarcyrheb-sun16" [root@tarkus root]#