Bug 39178
Summary: | Telnet to local host is inconsistant | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <davidkirk> |
Component: | telnet | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | davidk, davidkirk, pekkas |
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: | 2003-08-05 08:17: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
Need Real Name
2001-05-05 02:36:46 UTC
All the shell items mentioned above are misleading - sorry. I never knew about /etc/csh.cshrc and got confused. So that aside and the prompts running properly in bash or tcsh the inconsistancy still exists. If I run with Dump_log setup there are 3 things that happen. 1. user name goes to the remote - password: is not seen comming back. 2. user name goes to the remote - wassword: is sent back - the prompt is not sent. 3. Runs correctly. If I run the same script on solaris with Perl 5.005 it runs correctly all the time. If I run the same script on solaris to linux it runs correctly. If I run from linux to solaris it runs correctly. If I run from linux to another linux machine its inconsistant. If I run from linux to the same linux machine its inconsistant. The timeout happens in the sub waitfor in Telnet.pm I think the problem is Linux not responding fast enough to requests. If I pad the Telnet.pm with sleeps between login/waitfor and password/waitfor the script performs well. The results are still under test but so far I have had a run of 100 times in a row where it did not hang and executed correctly. Solaris can handle this and linux should also. Again this happens between linux machines - either one machine accessing itself or one linux machine to another. Linux box might be doing reverse-DNS lookups or ident-queries. If there are problems with either of these on the connecting box, it might take a while? Or do the waits happen after these have already been done? |