Bug 51212
| Summary: | pdksh-5.2.14-13 annoying tty message | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Mike Sklar <sklarm> |
| Component: | pdksh | Assignee: | Trond Eivind Glomsrxd <teg> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | roswell | ||
| 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: | 2001-08-14 18:33:25 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
Mike Sklar
2001-08-08 15:07:31 UTC
It doesn't happen for me - it works fine. The only change from -12 (shipped in RHL 7.1) to -13 is a rebuild, and I can't reproduce the problem. Have you done anything to your system, like compiling your own kernel? We (Red Hat) should try to fix this before next release. I'll do some additional checking and see if I can figure what is causing the message to be displayed, and if it is indeed coming from the ksh sources. I'm using the stock 2.4.6-3.1 kernel provided by redhat. asdfjkl$ rsh busted4 ksh: No controlling tty (open /dev/tty: No such device or address) ksh: warning: won't have full job control busted4$ uname -a Linux busted4 2.4.6-3.1smp #1 SMP Tue Jul 24 15:38:18 EDT 2001 ia64 unknown busted4$ Can you try util-linux from the rawhide push yesterday (util-linux-2.11f-8 )? No help. # rpm -Uvh util-linux-2.11f-8.ia64.rpm --force --nodeps Preparing... ########################################### [100%] 1:util-linux ########################################### [100%] # ksh ksh: No controlling tty (open /dev/tty: No such device or address) ksh: warning: won't have full job control # Can you check if this is a problem also after a restart? I'm not sure what could cause this... I'm confident it's not pdksh problem, and it doesn't happen for me with same ksh (but newer binaries all around it..) The issue appears to be rather transient. I don't get it on every single login. asdfjkl$ rsh busted4 ksh: No controlling tty (open /dev/tty: No such device or address) ksh: warning: won't have full job control busted4$ exit rlogin: connection closed. asdfjkl$ rsh busted4 busted4$ |