Bug 1450821
| Summary: | rlogin fails to connect rsh-server after updating util-linux-ng from version 2.17.2-12.18.el6 to 2.17.2-12.24.el6 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | rsh | Assignee: | Michal Ruprich <mruprich> |
| Status: | CLOSED ERRATA | QA Contact: | Leos Pol <lpol> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.8 | CC: | apmukher, asakure, baitken, cww, dbodnarc, dkaylor, eric.brunet, fkrska, gerardba, igkioka, james-p, jcastran, kabbott, kzak, lampe, lmiksik, luhliari, martin.moore, moscow1789, mruprich, psklenar, rick.beldin, riehecky, sean, snavale, thozza, tmilsond, zpytela |
| Target Milestone: | rc | Keywords: | Patch, Regression, Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rsh-0.17-64.el6_9.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, using the rlogin utility to log to a remote machine, the connection was closed on the remote side most of the time. This was caused by the forkpty() function which combines the openpty(), fork(), and login_tty() functions. When the child process handling the connection executed /bin/login, all open file descriptors got closed. This bug has been fixed, and now openpty(), fork(), and login_tty() are used separately instead of forkpty(). As a result, if needed, the parent process keeps the file descriptor of the child process open.
|
Story Points: | --- |
| Clone Of: | 1335670 | Environment: | |
| Last Closed: | 2017-05-30 17:09:32 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: | |||
| Bug Depends On: | 1335670, 1571314 | ||
| Bug Blocks: | |||
|
Description
Jaroslav Reznik
2017-05-15 08:53:25 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1377 |