Bug 19873
| Summary: | rexec broken on RH7.0 | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <hannaj> |
| Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | noarch | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-10-26 18:12:29 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: | |||
Rexec client does not work in RH 7.0. I localized the problem to the call to getservbyname in the rexec source. This call returns the wrong port number for establishing the remote connection. The port number returned by the following code fragment is port 2 instead of port 512 as listed in /etc/services service = getservbyname("exec","tcp"); port_exec = service->s_port; as revealed by gdb "print port_exec" after breaking on the appropriate line in rexec.c (132). Setting the value of port_exec to 512 corrects the problem and allows the rexec command to function correctly and terminate normally.